Cafe137
Cafe137
Not a bug, but an annoyance when looking at dev console
@Kexort More info: it seems the tokenservice endpoint provides the price from the (shut down) bonding curve. Therefor it is stuck at $0.45, which is highly off. This causes inaccurate...
There is also a `skip-postage-snapshot` flag which may be the correct one.
`ffe6d7fc805ede4581af1a01d9fcedf21332cfe3353d74a4961e53c360d06342` This hash can be downloaded by any node, but cannot be pinned. This hash has been uploaded with erasure coding.
I could reproduce this by depositing 1 PLUR to the chequebook. The transaction correctly appears under pending transactions. ``` { "transactionHash": "0x5238112041503c37ddc03594a58b17cf4c68c85e74d59184c328f5dede820eeb", "to": "0xdbf3ea6f5bee45c02255b2c26a16f300502f68da", "nonce": 23, "gasPrice": "1500256298", "gasLimit": 90000,...
- It is a good idea to have an option to explicitly instruct Bee on which feed resolution strategy to use - This development is not a hard requirement for...
Hi @acud, Thank you for the thoughtful response. 1. I was thinking of handling this logic inside the high-level api package, so that the resolution and retrieval internals can be...
@nugaon Why `/bytes` specifically? Why not include e.g `/bzz` too?
May be related to https://github.com/ethersphere/bee/issues/5123 ?