Acrux Net, 33 seconds.
A Solana fork with 50 ms slots. Three hubs, FRA, NYC and TYO, and every slot built by three validators that seal their blocks until all three commit, then merge into one order. 324 ms to finality.
It's running right now: acrux.computer/net
same attack, on a rule we're testing in the lab: local agreement, where a block goes in once 2 of 3 proposers attest it
today's rule skipped 16 slots, under agreement none, every cblock final in 383 to 387 ms
acrux.computer/lab/c38d527b-…
proposer 3 sent its commitment to one co-proposer and not the other, trying to get two different views of the slot
they attested what they actually saw, the vectors didn't match, nothing was agreed and the cblock got skipped. nobody gets a slot out of a split
acrux.computer/lab/dd837333-…
slot 4,366,946: every transaction in it was sent to all three proposers, so 24 came in across three blocks and 8 came out, duplicates dropped
then it's sorted by fee per CU, compute limit, hash, and packed onto four tracks, the same way on every validator
Chrome's warning on acrux.computer is gone, Google's Safe Browsing shows it clean now
thanks to everyone who sent a report, it helped
yeah, Chrome's flagging the site as dangerous right now. it isn't, review request is in with Google
if you want to help it clear faster, open this and tell them it's safe:
safebrowsing.google.com/safe…
it's cleared, Google has acrux.computer as safe again. thanks to everyone who reported it
2
86
Replying to @AcruxComputer @timtim2078552
cleared. Google shows no unsafe content on acrux.computer now, thanks for flagging it
1
52
proposer 3 sent its commitment to one co-proposer and not the other, trying to get two different views of the slot
they attested what they actually saw, the vectors didn't match, nothing was agreed and the cblock got skipped. nobody gets a slot out of a split
acrux.computer/lab/dd837333-…
the 20 ms commit window runs on each node's own clock, counted from when it saw the slot start. nothing in the protocol needs synced clocks
line 24 of the paper's Algorithm 1 next to the function that does it in acrux-node: acrux.computer/spec
fair questions, in order
the warning is Google Safe Browsing, flagged before the Windows build came off the site. the review request is in, same thing for the malware line
the cert is Let's Encrypt. all of theirs are 90 days and renew on their own
and it's running: slot 3,856,050 when I checked just now, acrux.computer/net
Replying to @AcruxComputer
Dear Dev Team,
I have a couple of questions.
-why is your site flagged as a high risk?
-why is your domain SSL only valid for 86 days?
-why is your product not working yet?
-why does google indicate that Acruxs is a malware suspucious software?
send a transaction 2-of-3 on Acrux and it goes out as three encrypted pieces, one to each proposer. any two put it back together, none of them can read it alone
measured: 8,000 lamports and 339 ms to executed, the same as sending it to all three in the clear
acrux.computer/send
validators on Acrux don't vote on every slot. four slots make a cblock and they vote once on it, every 200 ms
they vote after executing it too, so the certificate is on the resulting state. 80% of stake and it's final
Replying to @gabriel291990
it's Google's warning. the Windows build is off the site and the review is in, waiting on them now
three hubs today, FRA, NYC, TYO. a fourth one can be run by outside operators now
four of them register and join a hub through the registry with 1% of stake between them, and it goes active at the next bridge-epoch boundary. windows land on it from then
acrux.computer/docs/node/joi…
open any slot on acrux.computer/net and click a transaction, it's on every one
every transaction on Acrux now shows what its payer paid and where it went
one from the merged order: base 5,000, priority 38, inclusion 3,000, 8,038 lamports total. half the base fee, 2,500, is burned
after slot 4,752,000 those lamports are ACRUX
Fair question, and a good one.
We launched ACRUX on Solana for two reasons: to keep developing, and to keep the nodes running. Running high-performance nodes takes more capital than people think, and a PoC alone doesn't get funded anymore.
Real users are a separate problem. We got past the PoC stage and have a chain running, but connecting a new chain to real users takes a long time. So we launched where the users already are.
Building a launchpad and trading on our own chain alone would take a very long road, and building a community during that time is hard even before you count the cost. And if we had issued the token on a chain nobody used yet, who would have bought it?
The market is tough on newcomers. No infrastructure means no community, and no community means no infrastructure. If we had built an AMM instead of forking a chain, the odds that fomo would have supported it are very low.
So ACRUX started on Solana and comes over to Acrux through the bridge. From slot 4,752,000, bridged ACRUX is Acrux's gas.
We're not here to sell this as a finished product. We keep building because we didn't want to watch another L1 raise from VCs, wear "performance" as a mask, and pass the cost on to its users.
We're part of the same crypto community as you. Just writing down what's been on our minds.
Replying to @AcruxComputer
no fud here but a genuine question why did you not launch in your own chain? @AcruxComputer
7Evw4uxTxLGGEFEvXLUNYyc1J7PnFk9EYwTUFagARUX
We've tried to take every fair point seriously, and to give a real answer even to people who are critical of us.
People who doubt us are part of this community too, and many of them hold. So we've tried to explain to as many people as we can what we're building and why it works the way it does.
Answering the same unfounded accusations over and over has started to get in the way of development, so we decided to block one account.
If this keeps happening, we will likely make the same call again. We're saying it now to avoid any misunderstanding.
acrux.computer/net already tags every block genesis or external, so the first outside one will show up there
outside validators can get into Acrux's set from slot 5,616,000, around 11:30 UTC Nov 21
join a hub through the registry, stake ACRUX with the stock solana tools, and once you're in you propose your own blocks from your own machine. it has to sit near the hub, the block has to reach the other proposers inside 20 ms
acrux.computer/docs/node/joi…
ran an outside node into the FRA hub on the live net, from a desktop about 290 ms away
direct links to all four FRA co-proposers, 3,172 finalized slots re-executed, every state hash matching, and it kept up. proposing comes once it's admitted
acrux.computer/docs/node/joi…
and from slot 5,184,000, around 04:45 UTC Nov 21, you can stake ACRUX on Acrux with the stock solana CLI. how: acrux.computer/docs/sdk/stak…














