English is my second language. I learned it first (like all kids around my block) from unsubtitled animated cartoons. And later, from school.
Around age 7 I cracked a mystery. I found out that “doc” is an abbreviation for “doctor”. This triggered other memories of me hearing “what’s up” and understanding it is a form of salutation. And I got an epiphany: “What’s up doc?”, this is what that Bugs Bunny character was saying all along! I and all the children around my block were simply emitting similar-sounding gibberish up until that point, such as “watchoffduck”.
I had no idea…
About the moderated decentralized community
Feedback from the trenches of independent contribution, for the creator of Ethereum
Paraphrasing one of my patrons: Ethereum, I expect nothing from you other than what you yourself expect from your highest self.
DISCLAIMER(s): In the following, I am bound to hurt some feelings. Even the very soul of some people who I consider generous and well-intended. I do feel sorry for having to tackle this. I did lose some sleep over it.
- I am not tackling the conscious intent of any of the mentioned people — I cannot possibly know it. …
Read it on Github with syntax highlighting.
In Trustless-Bridging Ethereum (EVM) Blockchains — Part 1: Basics you saw that we have the tools to prove any momentary state change that happened on chain A, on another chain B, assuming that chain B has access to trustworthy chain A block hashes.
Today we will explore a mechanism for keeping smart contract state in sync between two EVM-based chains, as demoed in the following video:
Protocols usually implement replay protections to make sure malicious actors cannot execute state-changing transaction crafted on another chain. But purposefully implementing a mechanism for replaying state…
Read it on Github with syntax highlighting.
With the emerging proposals for integrating the EVM in Ethereum 2.0 ( https://ethresear.ch/t/executable-beacon-chain/8271), this EVM to EVM trustless two-directional bridge series comes at just the right moment. It can bridge Ethereum 1 to Ethereum 2. And the other way around.
A Symmetrical Light Client
A Light Client is a tool for validating chain data while storing the minimum amount of information.
The purpose of an on-chain light client is simple: storing the block hashes. These are enough to prove that “something” has happened on a chain of interest. …
Read it on GitHub: https://github.com/moral-upgrade-license/mul
The Last Flinch of a Dying Demon
There is an artificially induced financial stability in the world, which obscures the actual value of our work. If we are part of a guild — e.g. programmers, we expect our salary to be in a certain range, regardless of what we do. And these salary ranges have more to do with a market average, than with what is fair within the company. …
Environment
For illustrating our journey, we will use the Yul language. Yul compiles to both WebAssembly and EVM bytecode.
If you want to run the examples, it can be done with https://remix.ethereum.org:
- choose Yul as the compiled language, use the raw
calldatainput, check the return value using the debugger. - use the Yul+ plugin to compile, deploy and interact (you will need to comment out the
mslicehelper function)
The full code source can also be found at https://gist.github.com/loredanacirstea/fc1abd6345a17519455188d2e345f372
Prerequisites
Read the previous articles:
tags: Taylor, Ethereum, Solidity, Yul, eWasm, WebAssembly
This is a gradual introduction to my talk at the Solidity Summit, Wednesday, 29th of April at 2:50:00 PM CEST. Agenda.
Environment
For illustrating our journey, we will use the Yul language (that compiles to Ethereum 1.0 and Wasm bytecode).
If you want to run the examples, it can be done with https://remix.ethereum.org:
- choose Yul as the compiled language, use the raw
calldatainput, check the return value using the debugger. - use the Yul+ plugin to compile, deploy and interact (you will need to comment out the
mslicehelper function)
tags: Taylor , Yul, Ethereum, WebAssembly,ewasm
For illustrating our journey, we will use the Yul language (that compiles to Ethereum 1.0 and WebAssembly bytecode).
Anatomy of a Stack Runtime
object "ContractA" {
code {
datacopy(0, dataoffset("Runtime"), datasize("Runtime"))
return(0, datasize("Runtime"))
}
object "Runtime" {
code {
let _calldata := 256
let _output_pointer := 0
// Copy calldata at the _calldata pointer
calldatacopy(_calldata, 0, calldatasize())
// Read the first 4 bytes representing
// the signature of the called function
// https://solidity.readthedocs.io/en/v0.6.4/abi-spec.html#function-selector …
Imagine a space where you can freely explore a data set along several spatial indexes, such as in the following scene from “The Matrix”:
Types. Lots of subtype polymorphism.
Neo said “Guns. Lots of guns”. In reality, he would be in a logistics bottleneck: too many options and too much to carry. He could have said “Rifles. Lots of subtypes of rifles with attribute X.”, but that is far less catchy.
So, in this scene, our superclass type is Gun. However, there are many subtypes of guns and each type instance has addressability: (aisle_side, row_height, item_number). …
This is a proposal, following the principles laid out in The Unicorn article. It also further explores solutions to problems presented in I Have Gambled and Lost Devcon5.
It can also be found in https://github.com/one-unicorn/theunicorn. Discussions: https://gitter.im/one-unicorn/community.
Definitions
We define the plugem (the “m” signifies “multi”) as the type of plugin that “plugs” into multiple other components rather than into the plugin manager alone. Particularly, a plugem will discover other plugems in the execution environment, create the proper interfaces for them, and announce its presence to the other plugems.
Claim
We claim that the plugem software pattern will become the dominant form…
Loredana Cirstea
Building bricks for the World Computer #ethereum #Pipeline #dType #EIP1900 https://github.com/loredanacirstea, https://www.youtube.com/c/LoredanaCirstea
