RT @FamilyofTaygeta: #LAKA ~ There Is Always A Payoff. Beloved Friends Of Earth!. Choices Are Made Throughout Your Waking Dream. Some Of Th….

Another session with TARAN APP(funny thing +30m transactions processed) and @allanokothdev with @BasedKago guiding the session with some highlights on regulation concerns around fintech solutions.

Join millions who have switched to Grok.

Great insights from @HurupayApp CTO @allanokothdev and @element_pay taking us through their product journey courtesy of @ADAMUR_R and @BasedEastAfrica. Key point iteration as you move. #onchainsummer #BeyondCode

#securityconsiderations .1) Gas optimization - minimize cost to avoid denial of service .2) Reentry prevention - resource model helps block reentrancy attacks.3) Formal verification - mathematically prove critical contract logical correctness.

#functions serve as entry points implementing on chain business logic. Then basic structure of move project i.e., #movetoml (main config of project, info about project) #commondesign patterns: data as objects, one-time witness pattern (action only performed once object as proof)

Session 2 with @Mwende10Ashley briefing about #Sui resources (which ensure scarcity and prevent duplication of assets). Then objects which Sui core data structures can be owned, shared or immutable. #modules (contain code defining structs and fns for organization) and #functions

Session 1: brushing through the #Sui basics. NFTs, Slush wallet, why Sui

Side projects 👍🏿#SoftwareEngineering

Seeing more new people expressing genuine curiosity about Sui installation. Seeing their new experience with the process 👏. Big shout out to @ADAMUR_R for offering the platform. With @0x_Ochanda good job✅. Big shoutout to @pree_wanjiru ✅ #SuiBuilderPathway #Web3Kenya

Civilized man everywhere is, to some degree, in the position of Papuan victim of virtue. We have all kinds of aggressive impulses and creative impulses which society forbids us to indulge with supplied alternatives 'football matches', hardly quenching the thirst.

Crypto Innovations. Chain-Key Cryptography (DKG, threshold signatures) secures IC with key rotation. Randomness Beacons (R_h) ensure unpredictability. Partial Synchrony (safety always, liveness after GST) and f < n/3 fault tolerance make IC robust. #ICCrypto

Governance Layer (NNS). The Network Nervous System (NNS), a subnet itself, manages DAO voting, subnet memberships, and upgrades via its Registry & Scheduler. It provides public keys to Boundary Nodes and updates subnets’ memberships/code. #ICGovernance

Chain-Evolution & Execution. Subnets’ Chain-Evolution Manager handles epochs (length L), checkpoints (C_i), and threshold signatures (sigma_i). It garbage-collects old rounds, syncs via checkpoints, and reshapes keys/memberships. ICP tokens fund cycles for compute & storage.

Compute/Consensus Layer (Subnets). Subnets (e.g., A, B) host Replica Nodes running a Universal State Machine. Canisters (code + state) execute with cycles. HotStuff-style BFT consensus ensures safety (always) & liveness (after GST) with f < n/3 faults. #ICConsensus

Boundary/Edge Layer. Boundary Nodes receive HTTPS requests, using mTLS gateways, rate limiters, and ingress/egress translators. They fetch canister-subnet mappings from NNS, route messages to subnets, and verify replies with chain-key signatures. #ICArchitecture

Clients & UX Layer . Users interact with the IC via browsers or SDKs, sending HTTPS requests after DNS lookup. A Service Worker, injected on first load, handles auth & retries, forwarding requests to Boundary Nodes for processing. #InternetComputer #Blockchain

🚀 The Internet Computer (IC) blockchain architecture in a C4 diagram! Maps Clients, Boundary Nodes, Subnets, & NNS. 🔒 Chain-key crypto & 🛠️ BFT consensus shine! 📊PNG & thread explain the flow. #InternetComputer #Blockchain

⛑ Missing slivers? @WalrusProtocol leverages the two-dimensional (Red Stuff) encoding to allow completeness: every honest node can eventually recover and hold a version of every blob’s sliver after achieving the Point of Availability (PoA).

Using valid responses, reader reconstructs blob ( B ), combining the received slivers re-encodes the reconstructed ( B ). This results in a new blob ID' computed by hashing the new blob commitment (which includes metadata, such as file length and encoding type) #RedStuff.