The WAX blockchain has grown in usage and size pretty dramatically. On May 8th 2021, 307k unique accounts have executed 51 million actions. On February 8th, it was 18k and 6 million, correspondingly.
Back in February, a typical
nodeos setup would include a baremetal server with 3.5Ghz or faster Intel Xeon CPU, and directly attached SSD or NVME, preferably of datacenter grade. 32GB RAM was quite sufficient to cover the needs. The node state would be resided on the SSD storage. If ZFS is used with lz4 compression, the SSD I/O load was pretty low, less than 20% on average.
I’ve been in this blockchain space for a while, living through ups and downs in our great EOSIO ecosystem. These precious memories must not be lost, and they can actually work for the community.
So I’m starting the
cc32dninenft collection on WAX and later on EOS, with three major goals:
The first series is celebrating the first post in this blog, and it will be issued in 100 tokens on WAX:
Stay tuned, there’s more to come.
It’s a common struggle for every dapp builder that transactions may disappear from the blockchain while their blocks are not final. A microfork, resulting in a few blocks reevaluated and newly signed, might not include the transaction you’ve already seen. It might be dropped due to congestion, or because its timeout period is too short.
So if your service is receiving or sending payments, you always need to make sure that the transaction has survived and made it into an irreversible block. There’s a number of other transactions where it’s important to track the finality.
Most services are relying on…
Dan Larimer, former CTO of Block.One, has published a draft of EOS Community Governance Proposal. There’s over a 100 valuable comments by the time of this writing, and I’ll try to summarize my own thoughts here.
Elrond is a relatively new player on the blockchain market, offering a new and scalable platform for WASM smart contracts. In this article I summarize the differences, advantages and disadvantages between two platforms that I found while reading through Elrond documentation. As I’m mostly working in EOSIO environment, this is probably not a very objective review.
EOSIO accounts are 64-bit integers represented in alphanumeric notation. The user has a possibility to pick human-readable names. Account permissions delegate the authorization to public keys (or a combination of keys for multi-signature), and the system supports multiple ECC key standards. …
Recently I built and rolled out a Point-of-Sale smart contract on EOS, Telos, WAX, and 3 testnets. It will let anyone offer their goods and services on the blockchain, and accept payments in a token of their preference. Any project-specific token or wrapped BTC, USDT, and so on, will work.
The contract is inclusive, and it lets anyone start building their e-commerce solutions on top of it. I hope there will also be generic marketplaces where people can put out their goods for sale with a couple of clicks.
The buyer doesn’t need to do much: they only transfer the…
Automated token payments on EOSIO blockchains, especially on congested ones like EOS Mainnet, is a tricky business: transactions may fail because of insufficient CPU or NET or RAM resource, or may get dropped because of network congestion or microforks.
Typically a business that needs to send automated token payments is relying on a number of infrastructure services: it can check if a transaction is in an irreversible block by querying Hyperion or dFuse API, or set up its own Chronicle servers that would deliver such information.
My new Payout Engine is a holiday project that I wanted to implement for…
Here’s a new weekend project. I made a prototype database writer that takes all EOSIO contract table changes and writes them in a database. This allows searching through table rows in any possible way.
The source code is available on GitHub. The writer is taking Chronicle output for all table deltas and stores them in a table. the ROWS table is dedicated to one chain, in order to avoid locking conflicts. The script creates the table if it doesn’t exist. In addition, it creates two tables for tracking the reversible blocks, and to roll back in case of a fork…
The Associated Press has recently announced that they would publish the US election progress on EOS and Ethereum blockchains. At EOS Amsterdam, we quickly built a tool that collects this information from EOS in real time and stores in a MySQL database, which we opened up for public access.
The blockchain data is being collected using Chronicle software. Its development was first co-sponsored by 15 teams on EOS in 2018 (12 EOS block producers, Telos launch team, Worbli, and Lynx wallet), and later funded by two Telos WPS grants.
It’s a good step toward transparency in elections. We have now…
Privacy of business transactions is what enterprises are demanding from every blockchain project. So far EOSIO has not addressed that yet.
I wrote a design proposal on how the transaction privacy could be achieved. This design is a result of many months of thinking, experimenting, and collaborating with fellow colleagues in our telegram chat.
In short, the design proposes a 3-layer architecture:
The document is only a rough outline of what needs to be built, and there’s a lot of work ahead of us.
Telegram: cc32d9, EOS account: "cc32dninexxx"