Image for post
Image for post

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 changes or syncing state snapshots directly, can be a useful pattern for keeping assets on multiple chains or migrating from one chain to another. …


Image for post
Image for post

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.


Image for post
Image for post

Read on Github.

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 calldata input, check the return value using the debugger.
  • use the Yul+ plugin to compile, deploy and interact (you will need to comment out the mslice helper function)

The full code source can also be found at https://gist.github.com/loredanacirstea/fc1abd6345a17519455188d2e345f372

Prerequisites

Read the previous articles:


Image for post
Image for post

Read on Github.

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 calldata input, check the return value using the debugger.
  • use the Yul+ plugin to compile, deploy and interact (you will need to comment out the mslice helper function)

The code example below can also be found at https://gist.github.com/loredanacirstea/1aa18e33342b862d8dc76c01b12b7dbc. …


Image for post
Image for post

Read on GitHub.

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


Image for post
Image for post

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 of product delivery in the not so distant future. …


Image for post
Image for post

I have to excuse myself for the inability to make a summary of this essay. This essay is long and I made it as short as I felt possible.

I Have Gambled and Lost

Some of you might have seen or participated in my poll:

The poll was also posted on Reddit.

The outcome was:

  • 99/124 yes votes. I needed 200 yes votes
  • $726.41. I needed $1500

All donations have been returned. I withdrew my participation.

Notice that 25 votes were against Pipeline, without giving any feedback as to why. This is a lot.


Image for post
Image for post
An homage to the Devcon5, Osaka, avatar: https://devcon.org/

A Unicorn?

A Unicorn is a mythical ethereal creature — fed with the dreams and ideals of people. It is one of the few such myths that became decentralized, common to many cultures.

Let’s take off from Renaissance Europe, where the Unicorn is a symbol of purity and grace, a horse/goat-like animal with a white body and a long, unique horn, lion tail and either split or unsplit hooves, goat beard or no beard. Then, we arrive to read ancient Greek writings of natural history, where it was believed that unicorns exist in India, being the size of a horse, with a white body, purple head, blue eyes, having a horn colored in white, red and black. We fly to the medieval era, where it was associated allegorically with Christ, being tamed only by the pure-hearted Virgin Mary. …

About

Loredana Cirstea

Building bricks for the World Computer #ethereum #Pipeline #dType #EIP1900 https://github.com/loredanacirstea, https://www.youtube.com/c/LoredanaCirstea

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store