# PPLNS with job declaration

**URL:** <https://delvingbitcoin.org/t/pplns-with-job-declaration/1099>\
**Category:** Protocol Design\
**Created:** [August 28, 2024, 2:16pm UTC](https://delvingbitcoin.org/t/pplns-with-job-declaration/1099 "2024-08-28T14:16:11Z")\
**Posts on this page:** 1\
**Showing post:** 25

<div class="post-metadata">

**Author:** ![marathon-gary](https://delvingbitcoin.org/user_avatar/delvingbitcoin.org/marathon-gary/32/796_2.png) [@marathon-gary](https://delvingbitcoin.org/u/marathon-gary)\
**Post date:** [September 6, 2024, 4:21pm UTC](https://delvingbitcoin.org/t/pplns-with-job-declaration/1099/25 "2024-09-06T16:21:24Z")

</div>

> we can add the index in the merkle root I think that would be better

You could use the share index to determine Merkle tree ordering for the slice, this would prevent the scenario I outlined above. IIUC, this would also give the client some idea as the what the Merkle path should look like for a given share.

---

_[View the full topic](https://delvingbitcoin.org/t/pplns-with-job-declaration/1099)._