# 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:** 6

<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, 2:28pm UTC](https://delvingbitcoin.org/t/pplns-with-job-declaration/1099/6 "2024-09-06T14:28:25Z")

</div>

What prevents a pool from diluting shares within a slice/window?

I think this protocol makes sense but still suffers from the same issue that pools suffer from now, all of the validation data being used by miners is given out by the pool.

I think there’s a way forward with blinded signatures here that makes each proposal more robust. I’m not sure what that looks like yet but will post when I have someothing on the topic.

---

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