John Adler
John Adler
IMO, there's not really a distinction. Ethereum for example has logs == events, and so should we. Logs, despite the name, aren't meant for diagnostic purposes. They're meant to enable...
Good outline. The primary point is indeed to allow multiple otherwise-independent Forc projects to interact with each other seamlessly, rather than shared build artifacts.
This isn't really a _DoS_ vector (it's still a _DDoS_ vector, but those are unavoidable) since the cost of validating even a large transaction really isn't that much, and a...
It could be not part of the block in the same way the last commit doesn't need to be part of the block, if you define "block" as just the...
Ref: #315
Transferred to `celestia-node`. Poking @renaynay
To provide some additional context: since 1. Requests with a reserved namespace ID are concatenated contiguously, and 2. Messages are expected to be quite large, as they're supposed to be...
There is good reason to also separately bound the number of shares available to use for paying for messages, and all other requests with a reserved namespace ID: it avoids...
If predicates have a guaranteed upper bound on cost (e.g. by using gas metering), then sure. One thing we have to be careful of is that changes to the gas...
I'm leaning towards option B since it's a forcing function. In the current repo, there aren't enough eyes paid to the specs since it's one step removed.