pre-release update
small update for early testers of @octra network.
tmw we're planning to wrap up implementation of private txs (one of a bunch of features aimed at protecting your onchain data).
in the current testnet stage, every address owner has one main address, but
small notice: the repository with python CLI has been moved to the archive.
with the release of a new version based on Rust, you should switch to the new build.
the previous version WILL NOT be used and supported for security reasons and the absence of critical components for
there are a few important updates we want to release this week (delayed it twice to finish everything properly and not end up in a situation where we’d have to roll things back):
what’s coming in this release: a completely new client with built in contract support and no
last call: accept all incoming private txs (about 60% of hashes are still pending), sign the envelope with the old client from the archive if you removed it, if this is not done, these tokens will be lost forever after the transition to the new priv tx mechanism, try to do this
small minor update: in approximately two hours, the private tx transfer feature will be updated and will no longer be available (at all) on the previous client.
the new client will be available (tentatively) late at night with a wider range of features:
a much more secure
as part of tomorrow's pre-final update, the ability to encrypt and decrypt balances will cease in a couple of hours, but will resume with the new client (a week was enough to finish it)
remind you that unclaimed automated transfers will be lost forever
thanks all
earlier today at epoch 88169 the largest testnet update since its launch was applied, adding many new capabilities, this is the second to last update after which we can say the testnet looks as we originally planned.
added: abstractions over accounts (no longer just a “keypair
on the eve of a very significant testnet update, want to share a small and non-obvious feature of the contracts we’ll have.
contracts in octra are not just binary code written as a string in the chain’s db and interpreted by the vm through basic instructions. octra has a
btw, we’re not here to change anyone or anything, not trying to argue or prove a point — just sharing how we see things (what could be done differently, what might be improved, etc)
if someone finds it interesting or helpful, that’s more than enough for us
we’re just here to
happy to finally unveil octra evm
we’ve quietly been building a fully compatible hfhe+evm stack that keeps the spec intact, but moves all execution into a fully encrypted layer
currently an internal prototype, octra evm will be released open source this year for free use