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

<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, 3:03pm UTC](https://delvingbitcoin.org/t/pplns-with-job-declaration/1099/14 "2024-09-06T15:03:32Z")

</div>

The client gives the server a list of id’s (how is this list of IDs determined?) of shares they want to validate, I understand this piece. There is just no guarantee that the pool is providing accurate information. This is the same as using an API to query for shares.

What stops a pool from providing inaccurate or misleading share data? or omitting shares when requested?

Edit: Inaccurate or misleading shares would fail the Merkle inclusion validation piece. but omission remains un answered.

---

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