-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
No, so the way bytecode works is that there are a bunch of instructions in a string that the computer reads and executes. Some of those instructions are to set memory registers, or add values in registers, or write to persistent storage, or to branch execution path to a different part of the bytecode string based on the values of registers etc. Ack I might have linked you the yellow paper before. I meant to link the beige paper, which is a little easier to read, at the end there is a list of instructions as they exist in the EVM: https://github.com/chronaeon/beigepaper . The code commited to the blockchain is executed deterministically in the EVM based on the bytecode and the parameters sent in later transactions that a user makes to run that code, as well as the data in on chain persistent storage. e.g. I commit code like this: if you send me a 1 as a parameter, I send back the number 0, else I send you the number 1.
Related posts
-
How to improve the RISC-V specification
-
The Improved RISC-V Specification (latest WIP draft)
-
Wikipedia of Algebraic Geometry Will Forever Be Incomplete. (2022)
-
I do (and don't) prepare a talk for a tech conference. (2022)
-
Commonhaus Foundation: open-source innovation, collaboration, and sustainability