Kang3s
1.5K posts

Kang3s
@Kang3s
build OctWa ( https://t.co/vscIlsZ5Hb )

at epoch 729169, a consensus burn of 351,548,510.984 $OCT occurred based on the first proposal on the @octra network octrascan.io/tx.html?hash=2… this was done ahead of transition to mainnet beta and in preparation for external validator onboarding global info will update shortly

at epoch 729169, a consensus burn of 351,548,510.984 $OCT occurred based on the first proposal on the @octra network octrascan.io/tx.html?hash=2… this was done ahead of transition to mainnet beta and in preparation for external validator onboarding global info will update shortly






the first octra program with fully public inference for SmolLM2-135M (training, weight loading, and state are fully public) currently, it's only for informational purposes, because the full cycle is expensive (4k OCT) since it performs about 1 billion FP64 arithmetic ops so, wait for an update of the webcli with an interface for interaction via a wrapper (will be available tomorrow) now you can look at the process of loading weights: octrascan.io/epoch.html?id=… (using this epoch as an example) example exec with resp: octrascan.io/tx.html?hash=a… * the program is verified and completely open


Can someone more technically inclined tell me if this is the right way to think about @octra: its relationship to privacy is similar to Celestia and data availability? The L1 operates like any other, with $OCT as its native gas. However, any part of the stack in the chain and app infrastructure can opt to integrate using Octra to encrypt and compute said piece of the stack. Where am I wrong and what am I missing?











