https://hackerpaper.kaipfister.de/p/2201.05574/Collected HN comments and submissions linking this paper.enMon, 02 Nov 2026 11:16:22 GMThttps://news.ycombinator.com/item?id=36086592urn:hackerpapers:mention:2201.05574:36086592Fri, 26 May 2023 16:46:19 GMT<p>&gt; The Web3 API is the API exposed by the full node themselves, and it exposes the requirement of the ethereum protocol (example: the nonce, the encoding scheme for smart contracts, the primitives operation of the EVM, etc) . It is then wrapped inside libraries in different languages (and you can write your own) but the underlying stuff is constrained by the blockchain protocol itself (you cannot make the nonce mechanism less stupid no matter how hard you try, for instance, the nodes will just reject your transaction if you don&#x27;t follow the dumb protocol). The nodes expose the JSON-RPC API…</p><p><a href="https://hackerpaper.kaipfister.de/p/2201.05574/">Paper and discussion history</a>. A mention is not an endorsement.</p>econ.GNhttps://news.ycombinator.com/item?id=29969184urn:hackerpapers:submission:2201.05574:29969184Mon, 17 Jan 2022 17:44:59 GMT<p>Analysis of EIP-1559: Transaction Fees, Waiting Time, and Consensus Security</p><p></p><p>1 point; 0 discussion replies on HN. <a href="https://hackerpaper.kaipfister.de/p/2201.05574/">Paper and source history</a>. A submission is not an endorsement.</p>econ.GN