ΞLIZARD retweeted
mini comment on the mini roadmap: a new release marker for devnet will be available in a couple of hours and the release marker and info for main network are expected later today (there was a lot of delicate work involved, we did our best) – at London, England
mini-activation roadmap (during the day for the next epochs):
0 - rpc shutdown (and preparation of a 2+ hour window)
1 - snapshot of the state (of both networks, mainnet and devnet), the snapshot hash will be available separately,
2 - sequential activation on foundation nodes (we will launch a planned merge on our nodes and wait for all rules to activate on the mainnet, this is done to ensure all rules are in place and properly debugged),
3 - monitoring the progress of epochs, after 1000 epochs, a public set of configs for connecting external validators is published (the mainnet becomes uncontrolled, validator participants contribute bonds and begin participating in the treechain).
we ran several test runs over the weekend and confirmed everything was fine, so we're starting the process step by step, we'll publish info about the activation window shortly (this could be considered the snapshot time), everything was boiled down to a few simple steps, and we don't expect any significant issues today.
the reward model will be published separately, as the mainnet differs significantly in supply and reward formation, as well as the OU fees for ops carried out.
** all rewards earned by validators in the devnet for the entire period will be available to them in the main net (every bit processed will be counted and fairly determined)
thanks everyone.
ΞLIZARD retweeted
If you lost money on solana:8PzFWyLpCVEmbZmVJcaRTU5r69XKJx1rd7YGpWvnpump token, please reply to this post with roughly how much you lost :)
Please amplify the post if you reply. TY!
ΞLIZARD retweeted
mini-activation roadmap (during the day for the next epochs):
0 - rpc shutdown (and preparation of a 2+ hour window)
1 - snapshot of the state (of both networks, mainnet and devnet), the snapshot hash will be available separately,
2 - sequential activation on foundation nodes (we will launch a planned merge on our nodes and wait for all rules to activate on the mainnet, this is done to ensure all rules are in place and properly debugged),
3 - monitoring the progress of epochs, after 1000 epochs, a public set of configs for connecting external validators is published (the mainnet becomes uncontrolled, validator participants contribute bonds and begin participating in the treechain).
we ran several test runs over the weekend and confirmed everything was fine, so we're starting the process step by step, we'll publish info about the activation window shortly (this could be considered the snapshot time), everything was boiled down to a few simple steps, and we don't expect any significant issues today.
the reward model will be published separately, as the mainnet differs significantly in supply and reward formation, as well as the OU fees for ops carried out.
** all rewards earned by validators in the devnet for the entire period will be available to them in the main net (every bit processed will be counted and fairly determined)
thanks everyone. – at London, England
its time to update the mainnet and release it in the form it was originally planned, the very first vision is probably the only correct one
special thanks to all the validators and participants who supported the devnet and continue to do so - now it's time for the mainnet, permission less access is planned for tomorrow/the day after (the exact time is unknown, any second now)
everything needed to run a mainnet node will be available in a separate release, thanks everyone
ΞLIZARD retweeted
its time to update the mainnet and release it in the form it was originally planned, the very first vision is probably the only correct one
special thanks to all the validators and participants who supported the devnet and continue to do so - now it's time for the mainnet, permission less access is planned for tomorrow/the day after (the exact time is unknown, any second now)
everything needed to run a mainnet node will be available in a separate release, thanks everyone – at London, England
ΞLIZARD retweeted
Shareholders,
In preparation for Net Forge official launch we will begin adding wsNET/USDG liquidity from the RWA Sleeve today.
More Soon.
ΞLIZARD retweeted
So what is the implication of GeoRefine GLC? It demonstrates that any uncompressed BF16 model weights may be transformed into alternative data representations that enable both faster decoding and serving, and much smaller storage than ordinary dense encoding with no quality loss.
Qwen3.8-27B at 1.53× fully lossless compression. Blackwell at 128 users: 1.34× throughput vs BF16, with MTP enabled.
huggingface.co/Tsotchke-Corp…
ΞLIZARD retweeted
Any existing inference provider can immediately save ~35% of the VRAM consumption and increase their throughput just by using our codec. Beyond this—GeoRefine's geometrically guided quantisation, pruning, and certified repair system will even more dramatically reduce model sizes.
ΞLIZARD retweeted
GeoRefine GLC v2 is live: completely reversible, fully lossless compression for AI model weights.
Our Qwen3.8-27B package achieves 1.53× compression: 55.6 GB → 36.3 GB: every original weight can be recovered bit for bit.
Qwen3.8-27B at 1.53× fully lossless compression. Blackwell at 128 users: 1.34× throughput vs BF16, with MTP enabled.
huggingface.co/Tsotchke-Corp…
ΞLIZARD retweeted
Qwen3.8-27B at 1.53× fully lossless compression. Blackwell at 128 users: 1.34× throughput vs BF16, with MTP enabled.
huggingface.co/Tsotchke-Corp…
ΞLIZARD retweeted
Qwen3.8-27B at 1.53× fully lossless compression. Blackwell at 128 users: 1.34× throughput vs BF16, with MTP enabled.
huggingface.co/Tsotchke-Corp…
ΞLIZARD retweeted
The elegance of the NetNet protocol continues with inverse bonds which allow you to redeem your NET from the treasury for 98.5% of NAV ($162.91) and burns the NET.
To date, we’ve seen 9,582 NET burned (6.27% of total supply), and users have redeemed a total of $1.54m resulting in the NAV increasing due to redemption value being slightly lower than NAV.
Inverse bond capacity per epoc is 1% of the total liquid USDG maintained at a 30/70 split between the liquid USDG and yield bearing Morpho vault.
If the market price (currently $160.82) falls below NAV, it’s arbitraged typically to within 5% of NAV because of the 5% buy tax.
We saw market efficiency arbitrage a single 2,208 NET $346k ($156.52 per NET) market sell last night which brought the market price back right in line with NAV as of this morning.
The treasury (ownership revoked and immutable) still sits at $24.9m in USDG. NET is essentially a stablecoin with only upside while staking rewards remain at zero.
NetNet is battle-tested new financial art.
ΞLIZARD retweeted
Binance's initial investigation suggests that the security incident may involve a compromised DevOps engineer’s laptop, which allowed an attacker to gain access to a service container and submit unauthorized withdrawal transactions. We have found no evidence of any wallet private key leak. We will share a detailed technical post-mortem once the investigation is complete and the facts are fully verified.
The estimated total impact sits at around $6.3B. We have worked with blockchain partners to freeze affected assets, with ~$3 billion frozen on-chain so far.
Binance will cover all losses from the SAFU fund and the company’s funds. User funds are safe. We will also publish an updated Proof of Reserves once the remediation is complete.
As an immediate precaution, Binance has:
- temporarily suspended deposits and withdrawals while security checks are completed;
- revoked the affected address authorisation;
- engaged law enforcement and blockchain intelligence partners to trace and recover funds.
Our teams are working around the clock to resolve this issue safely and thoroughly. We are working closely with our law enforcement partners to confirm the identity of these criminals and bring them to justice.
Please rely only on official Binance channels for updates. Please feel free to contact Binance Customer Support if you have any further questions.
binance.com/en/support/annou…
