Last week my colleagues at open food chain tweeted this out, and it got me thinking to check how easy it was to find public agriculture data? My first search was very US centric, so I added a couple of countries I have interest in working in.

US agriculture data sources

The first search produced the following results.

But this wasn't very useful to me, who has a casual interest in agricultural data. Admittedly, I know I know nothing, and there are thousands of people smarter than me on this subject and thousands of more AIs being programmed to decipher this information.

Greece & Thailand agricultural data

I will limit my search to at least a couple of countries I have an interest in doing some work in.

Get ready, it all sounds Greek to me!
Having learned a little bit of Thai & Greek language, Thai is easier to pick up, but much harder to read. Another get ready situation coming on this quick search for agricultural data.

And when I follow these search results I am greeted with info in Greek & Thai languages! So it's not quite a dead end yet, I can look up agricultural data formats maybe?!

Agriculture data formats

I have 20 years of on & off experience reading data on a wire and following protocol specifications to work out what is going on. Although I'm not an expert (anymore) on data formats, I have a few old tricks up my sleeve I can count on from time to time to get into the flow of the data.

So I am led to believe stuff exists - but I wonder how accessible this stuff actually is?

Future of sharing UTXO data formats for agriculture

Through the development of open food chain solution of supply chain tracking and batch matching between suppliers, I've learned to really appreciated the UTXO model for it's simplicity and low barrier to entry for sharing data.

In a private presentation to the open food chain team, I have expressed that it is possible to share field data publicly and not in a data silo that becomes a cost center to an organization to secure & maintain.

Additionally, when a larger organization (for instance Bayer) buys out a smaller organization that has conducted field tests on larvae growth in certain areas, the larger organization more than likely has no interest in continuing or sharing the data from the earlier studies. Sometimes it's too hard to make available, and sometimes it is wrapped up in company policy, and sometimes it is tin-foil hat profit motives. As a public, we don't know.

How to access UTXO agricultural data

The way to access agriculture data stored on a blockchain is the same as any other blockchain data - blockchain explorers & the explorer APIs. Wondering about scalability? Well of course, we can add caching between the client and the blockchain if it is a public resource. However, with anybody able to sync a public blockchain, getting a high performance data source is easy to connect to.

An MVP of burger tracking at Blockchain Burger by ChefChain

The game is a simple turn based economic business simulation game, like "Lemonade Stand" or "Dope Wars" or "Pizza Tycoon" or others from that era of games. It is currently in development, written as a light client targeting a komodo smart chain. The light client uses electrum client to sign the transaction and an explorer to fetch utxos & broadcast the signed transaction.

Basic outline of some api calls to send a transaction.
Simplification of what happens during a game action

I asked Verus lead dev Mike T about the future of PBaaS light mode support in discord, to which he gave helpful responses that were encouraging to consider the future for supporting my game effort on a Verus chain as well.

Electrum will work for a PBaaS chain, but is insufficient to make decent apps that use even a medium amount of Verus features. We are moving to a Verus extended BitCore server for lite mode functions and deprecating ElectrumX for foundation or recommended use. The next update of Verus Mobile will be the first on the new interface, which enables it to access all of the new APIs, smart transaction capabilities, DeFi, etc., as well as information needed for z-transaction support in light mode, though to move z-transactions away from lightwalletd requires additional work. A new version of Verus Mobile with this interface is near ready, and has only been waiting for some authentication and ID provisioning protocol improvements that are coming along nicely.

So, whatever I created on a Komodo Smart Chain will likely work without any changes on a Verus PBaaS chain. Further, I asked about the bitcore wallet server that Verus is moving towards to support more of the Verus enhanced functions relating to the bitcore-server.

We have Verus enhanced servers in the VerusCoin repos. They have Verus capabilities exposed, and there are much more advanced enhancements in progress that will be pushed to the VerusCoin repos before PBaaS. As a dev, it should be obvious from the changes we already made, how it will work. Non-Verus or generic repos won’t support Verus capabilities any more than Electrum.

For the moment, and things to watch are still in the rpc client, as Mike mentioned here

So, it turns out that right now, we're using the Verus version of bitcoind-rpc. We plan to cover it with a Bitcore caching layer, but the full API will be exposed via that server. Here is the current version being used in testing, and it will be updated with new functions before release:

Verus enhanced bitcoind-rpc

I first looked at the Verus enhanced, then looked at Mike's fork of new development he has made.

Verus enhanced bitcoind showing 1 commit ahead of upstream.
Only 1 change from upstream, which added getIdentity and a few other komodo related calls.

Then in Mike's branch some simple rewiring of the existing methods call specs, by loading it with a no-wallet by default object - a method of enhancing an existing library I enjoy, which was used to disable zCash parameters requirement on public-only smart chains.

Re-wire the initialization of functions
Re-wire the initialization of functions

The subtle differences between the apisNoWallet vs apisWithWallet is clever, for instance Verus Identity method, getIdentity has different parameters passed to it whether there is a wallet loaded or not. Handy to know for the future.

Then we start to see the Verus enhancements come into the bitcoind-rpc library. In particular, the apisWithWallet have some of the cool features Verus DeFi offers - defining a currency & blockchain identity to name a couple.

The remainder of the commits didn't seem too interesting, with the addition of a httpserver for comms.

Verus Bitcore Enhancements

Bitcore is the software that makes a whole bunch of blockchain features possible. Bitcore integration in the komodo code base enabled high performance blockchain lookups - which Verus inherited as a friendly fork. The javascript library that is used with the explorer, had some further Verus enhancements for reserve currencies.

Then some PBaaS functions and identity added to the bitcore library.

Verus Blockchain Explorer Reserve Currencies Spent

This then showed up in a transaction on the PBaaS testnet VRSCTEST, showing that there's a new dimension of supporting game functions that can be used, to make compelling economic simulation games on Verus!

The explorer also supports nodejs v9, compared to the original komodo explorer that is supported with node version 4. The Tokel explorer also supports enhancements for displaying NFT information, but these have not been investigated yet.

Placeholder page for blockchain identity basics.

Placeholder page to currency definition.

We the consumer in this web3 world are told that it democratizes access to participation, influence & opportunity. In this video by Verus community member @creativeninja, the points of centralized components of the decentralized world are highlighted. And it begs the questions of which mix of decentralized function is ok?

The transcript from this talk is available at the KomoDeFi transcripts repo on github.

Decentralized Token Distribution & Centralized Infrastructure

In the talk, Bradley mentions Infura, Alchemy & MetaMask as examples of dApps that run on centralized infrastructure. The article about blockchain nation states linked in the opening paragraph cites BNB Chain as this centralized infrastructure, but decentralized token distribution.

A network can be decentralized when it comes to its token distribution but at the same time run on a centralized infrastructure. Binance Smart Chain is a good example of that.

Decentralized Nodes & Centralized Governance

Governance means different thing to different parties, but tackling the blockchain governance problem is being done by multiple projects. In my experience with the Openfood Chain, the governance is centralized around the industry consortium by forming a governing foundation.

Another network could be decentralized when it comes to number of nodes and physical locations of nodes, but centralized when it comes to governance. Cardano is a good example of that model.

Fair Launch - No ICO - No Premine Decentralization

Bradley states:

consider Bitcoin the most well- known Fair launch blockchain protocol it had no Ico no pre-mine no VC company backing and no Founders funds

The Verus Coin project also started in the same spirit. As a no-code solution for creating blockchains, the launch of the PBaaS mainnet approaching, decentralization for future projects has a bright future.

Future Decentralization

With some 15,000 discord users, it is the most number of possible users for further decentralizing new applications and protocols.

Paraphrasing what @creativeninja says of the former CEO of Twitter @jack opining for:

it's critical we focus our energy on truly secure and resilient Technologies owned by the mass of people not individual not individuals or institutions only that foundation will provide for the applications

@here Hello everyone, just so that everyone can find it, this is the Open Food Whitepaper, where you can learn more about how our technology works. You can also find this on our website where you'll additionally find our pitch deck.

Agri food traceability: Good read

Komodo team member smk762 guides us through the 0.5.4 version of atomicDEX wallet.

The atomicDEX wallet has added 13 new protocols since this video was created, so there's even more to see!

The atomicDEX page shows the most recent commits & issues, so there's an easy way to see what the developers of the most versatile multi-protocol wallet have been up to from their work pushed to github.

@everyone Announcing v0.9.2-3, NON-MANDATORY, FOR MAINNET -- CRITICAL FOR TESTNET USE This release has no mainnet changes.

New use cases live on testnet

- Ability to create new .veth VerusIDs that are priced in USDC, paid for using $100 woth of Bridge.VETH, and useful as both self-sovereign VerusIDs and also to define Ethereum mapped currencies for use on Verus, Ethereum, and PBaaS chains across the network. While this was previously in the protocol, we will shortly roll out the Etherum bridge update that will let everyone easily use it.

- Full support for defining mapped currencies and easily exporting any PBaaS currency as an ERC20 to Ethereum's Rinkeby testnet. Using mapped currencies, you can even create your own provable, auditable, mapped stable coins, collateralized 100% provably by the protocol, using any ERC20 currency on Ethereum, such as DAI, USDC, or any other currency at all. Either root VerusIDs or.veth IDs can be used to create Ethereum mapped currencies.

- Ethereum bridge website now recognizes and makes it easy to use all exported, ERC20 PBaaS currencies and all mapped currencies in the new user interface.

With v0.9.2-3, and the soon to be launched update to the ETH bridge, ready now and expected on testnet within the next couple days, you can now create .your own, self-sovereign, permanent name.veth identities, and map currencies to them. For example, MYCOIN.VETH could be mapped to USDC, creating a fully decentralized, provable, auditable, currency that can be sent back and forth from Ethereum's USDC to Verus or any PBaaS chain as MYCOIN.VETH. You can do the same with any currency on Etherum and any identity you control that is either a root or *.veth VerusID.

The rest of these release notes are the same as the prior release. Drop by pbaas-development to help get PBaaS ready for mainnet!

CLI release:

GUI release:

Hello @everyone

We promised and we are delivering! Thank you to all TKL supporters for helping us kickstart the project and for your continuous contribution.

This release includes long awaited Time Lock transactions changes.

Download this release to see your time lock rewards:

Check your rewards at

Thank you again for supporting us and believing in us at early stages of the project

- Added functionality for displaying time lock transactions
- NSPV-js updated to send/receive time lock transactions
- The main Dashboard is a Wallet now
- Added a widget to display token and TKL addresses at one place
- More organised history widget
- New Send Widget which shows the Spendable and Locked amounts depending on whether the user has locked transactions

- Fixed incorrect TKL price on the main view of the dapp
- Fixed incorrect TKL amounts for transactions with decimals
- Extended transaction value parsing Please reach out to us if you have any questions 🤗

Thank you again everyone for being part of Tokel! Tokel Team

Experience Crypto
© 2022