@achamayou @eddyashton, regarding the services with lots of DRs, shall we introduce a new request parameter to ask for the endorsements chain explicitly?

Possible options

• I want the full chain
• I want a shortened chain (not really sure how, create a chain digest or smth?, or counter-sign only the original service identity at the time of TX in question, as we do for current endorsements)
• I don't want a chain

@maxtropets we can do, but the chain should only get substantial if you ask for receipts that are many DRs ago. If you ask for recent receipts, it'll still be short. Having an option to skip endorsements definitely makes sense, and an endpoint to just get the chain (or even the chain in a tx range).

Proposal:

GET /node/receipt | x-ms-ccf-txid: 5.578 => receipt + full chain
GET /node/receipt?asof=now | x-ms-ccf-txid: 5.578 => receipt + full chain
GET /node/receipt?asof=7.999 | x-ms-ccf-txid: 5.578 => receipt + chain from 5.578 to the latest identity as of 7.999
GET /node/receipt?asof=5.578 | x-ms-ccf-txid: 5.578 => receipt + no chain