Since the first post, a lot has changed.
Flow, swap, NFTs, and the overall UI/UX have all come a long way, and it’s starting to feel much closer to the product we had in mind.
Some things, including colors, may still change, because a lot can still evolve from here. #wallet #algorand #selfcustody #defi #crypto #buildinpublic #uiux #productdesign

After going through real wallet pain in Algorand, I decided to build the thing I wanted to see. Core is working, testnet and mainnet are tested, and I’m taking my time with the rest. I stopped waiting and started building. A new kid on the block is coming to the ecosystem. Still early, still moving carefully — more when the time is right. #Algorand #buildinpublic #DeFi #algodev

The full-stack multi-asset architecture is officially live. 🔨⛓️ Wrapped up the final layer of the CryptoLwei protocol sandbox, taking it from a raw backend terminal to a dynamic multi-token application ecosystem. What’s running now: • ASA-Style Token Provisioning: Minted $GLITCH with customized metadata extensions and total supply tracking. • Multi-Asset Ledger State: Upgraded the node balance sheet to store and track varying token balances simultaneously under one wallet address. • Gas Burning Mechanics: Successfully integrated programmatic protocol fee deductions ($LWEI) from the creator wallet on asset generation. • Full HUD Data Integration: Built a customized frontend terminal complete with automated address state binding and an integrated explorer lookup engine. Mints, transfers, state transitions, and gas burns are all verifying seamlessly across the immutable ledger. This marks the end of the sandbox phase. This entire proof of work is heading straight to GitHub next. Building the core infrastructure from scratch changes everything. 📦🚀 #BuildInPublic #CryptoLwei #Web3Infra #ReactJS #PythonDev #FullStackWeb3

Decided to build a custom blockchain network protocol from scratch in Python to really master core Web3 infrastructure mechanics. Meet the CryptoLwei Protocol. 🛠️📦 What’s under the hood: • SHA-256 Chained Ledgers (Immutable state verification) • Proof-of-Work Mining Engine (CPU nonce puzzle solving) • Asymmetric Cryptography (RSA Key pair wallet generation) • Active Mempool with gas fee priority sorting • Live Node API Layer (Wrapped via Flask for RPC-style execution) Hooked up a second terminal client, broadcasted a transaction, watched the mempool prioritize the highest tip, and successfully mined Block 1 with a valid zero-prefix hash over a local network loop. Understanding the protocol layer completely changes how you look at the dApp layer. Next up: building out a local state machine to track wallet balances across blocks. Coding is cool, but understanding the foundational math is cooler. 🧠💻 #BuildInPublic #CryptoDevs #Web3Builders #AlgorandDev #SolanaDev #ProofOfWork #Mempool #NodeEngine #CryptoLwei

The result? A live, web-accessible node running locally, creating immutable block links, and maintaining complete network health. If you want to truly understand gas wars, consensus rules, or RPC layers, stop just reading whitepapers and go build a local ledger. On to the next phase! 🏁 #Web3Infra #Cryptography #BackendDev #PythonDev #SystemsEngineering #BlockchainArchitecture #CryptoLwei

Been building an ASA minting dApp on Algorand and testing both FTs and NFTs with ARC‑3 metadata IPFS logos. Setup: •FTs: large total supply, decimals > 0, url → ARC‑3 JSON (name, unitName, decimals, description, image, image_mimetype).

 •NFTs: total = 1, decimals = 0, similar ARC‑3 JSON with image.
 Observed behavior across tools: •Lora Pera Explorer: read ARC‑3 metadata, show logo description, and correctly mark fungible vs non‑fungible from on‑chain params.

 •Pera Wallet: some fungible ARC‑3 assets with logos appear under the NFTs tab, even though they have 100M supply and 6 decimals.

 •Defly: assets sometimes show as ? / no name or logo depending on metadata URL format (ipfs://... vs https://gateway/...) and how the ARC‑3 URL is encoded.
 I’m trying to align tooling with wallet expectations for both FTs and NFTs, so creators get predictable results. @PeraAlgoWallet @deflyapp is there a recommended pattern (ARC‑3 vs ARC‑19, URL format, metadata_hash, etc.) to ensure: •FTs show as “tokens” and NFTs as “collectibles” in your UIs, and •logos / names resolve reliably across wallets? Not criticizing—just looking for guidance so dev tools can follow the same rules your apps are using. Any pointers or docs appreciated. 🙏 #Algorand #AlgorandDev #ASA #NFT

Took ASA_TERMINAL on Algorand from v1.0 → v1.1.
Main goal: make FTs behave like FTs and NFTs behave like NFTs across wallets. In v1.0, giving everything rich metadata logos meant some wallets started treating fungible tokens like NFTs. Wrong tabs, confusing UX. v1.1 (live on testnet) fixes that: •Dual mode: Fungible Token / NFT / Collectible •FT mode: minimal metadata, no on‑chain logo, no #arc3 → shows up correctly as a fungible asset •NFT mode: full ARC‑style metadata logo upload, total = 1, decimals = 0, metadata_hash = sha512_256(url) → lands in the NFTs tab as it should •4‑step terminal pipeline: prepare metadata → createAsset() → user opt‑in → claim supply •Every mint sends an extra 0.3 ALGO to the contract account to keep it funded so it doesn’t silently run out of balance as usage grows •Sticky header, themed wallet modal with dynamic network info, and a soft reset that clears the form logs but keeps the wallet mode Honest trade‑off in v1.1: •NFTs get full logo metadata at mint time. •FTs stay “clean” at mint time so wallets stop misclassifying them. Logos can be added later via other tooling. #Algorand #AlgorandDevs #AlgorandNFTs #ASA #DeFi #Web3Builders

🛠️ Web3 Build Log: Built a custom React frontend terminal and successfully wired it to my deployed Algorand smart contract factory. Ran the full integration loop on Testnet: automated the pipeline to mint the asset via the contract, execute the wallet opt-in, and securely claim the supply directly to Defly. Encountered some state param bugs on the asset identity mapping during the initial run, but the underlying orchestration pipeline is fully functional and live. Ready to patch the form bindings next. #Algorand #Web3 #BuildInPublic #BlockchainDev #AlgoDev

🛠 The "Building in Public" Report: Environmental Cleanup The Problem: I had AlgoKit installed through two different managers (Homebrew Cask and Pipx). This caused a path conflict where my terminal was trying to run the CLI using an old Python environment inside Anaconda. • The Symptom: Unhandled ImportError: cannot import name 'AlgorandClient' from 'algokit-utils'. • The Reason: Anaconda was "hijacking" my Python path, forcing AlgoKit to look at outdated libraries instead of the fresh ones. The Solution (The "Scorched Earth" Method): 1.Uninstall everything: brew uninstall algokit and pipx uninstall algokit. 2.Deactivate the "Base" environment: conda deactivate to stop Anaconda from interfering. 3.Clean Reinstall: Used Homebrew for a fresh, isolated install. 4.Align Python: Used pyenv to set a global version (3.13.5) so the terminal isn't guessing which Python to use. The Result: algokit doctor is 100% green. LocalNet is live. Ready to build. #Algorand #AlgoKit #Web3Dev #BuildInPublic #Python #CodingStruggle #BlockchainDeveloper

Check out the blog post 🤓 info.algorand.foundation/e3t…

Algo fam, huge upgrade for builders 💚 The AlgoKit Utils beta is live with: •One unified AlgorandClient for TS Python •Signer-based accounts (no raw private keys) •Built-in HD wallets (BIP-44, ARC-52) •ARC-56 app specs by default This is a big step toward AlgoKit 4.0 and a smoother prototype → production path. #Algorand #AlgoKit #AlgoKitUtils #Python #TypeScript #Web3 #DevTools #AlgorandDevelopers

$LWEI Update — for those watching 👁 Yes, Jupiter is showing 4 warnings. Here's what they actually mean: ⚠️ High Price Impact → No trades yet. Bonding curve hasn't started. That's intentional. ⚠️ Not Verified → In the manual verification queue. Verification is a core goal — it will be done right. ⚠️ Low Liquidity → Pool fills as the bonding curve grows. We're at the start. ⚠️ Low Organic Activity → No trades, no activity yet. Simple. Here's how $LWEI is designed to grow: 1️⃣ Bonding curve phase — price discovery on Jupiter Studio 2️⃣ Graduation to Meteora — automatic when threshold is hit 3️⃣ Liquidity permanently locked — no rug possible 4️⃣ Full Solana ecosystem access — Jupiter, Raydium and beyond We're not pumping it. We're building it. $LWEI is us. We are $LWEI. 🧱 CA: 7M9zHgCGZhZtoSUREAjgYMaioBBsfGPDvUP4F9Stjupx #LWEI #Solana #BuildInPublic #Web3 #CryptoLwei #JupiterDEX

cryptolwei.com runs on: — 1 HTML file
— 1 CSS file
— 1 JS file
— 1 font import That's it. No frameworks. No npm. No build tools. Just clean fundamentals, written code. 🧱 As we grow and ship real dApps — the stack evolves.
But this is where every serious builder starts. #BuildInPublic #Web3 #Algorand #Solana #WebDev #CryptoLwei 🔥

Building everything from scratch and evolving. Step by step. The site you see at cryptolwei.com? Pure HTML, CSS & JS. No frameworks. No shortcuts. As the project grows and we start shipping real apps — we move to React. But first, master the foundation. This is how you build in Web3 with intention. 🧱 #Web3 #BuildInPublic #Solana #Algorand #WebDev #HTML #CSS #JavaScript #CryptoLwei #OnchainBuilder #Web3Dev #BlockchainDev

Just updated cryptolwei.com 🔧 — $LWEI live with CA Jupiter trade button
— Dual-chain strategy: Solana for liquidity, Algorand for utility
— The Lab is open 👀 Something is cooking. Not ready yet. cryptolwei.com

Lweicoin Ecosystem Update: Transparency & Progress 🛡️ We’ve noticed some automated scanners (Solscan/GoPlus) flagging $LWEI as "Not Trusted." Here is why this is a green flag for our long-term builders: 1️⃣ Status #198: We are currently in the @JupiterExchange verification queue. "Trusted" status is a manual switch that flips once verification is complete. 2️⃣ Technical Authorities: Our Metadata and Mint authorities remain "Ok" (Active). This is essential for: • Powering our 12-month linear vesting schedule. • Executing the upcoming Solana ↔ Algorand bridge (Python/PuyaPy). 3️⃣ Builder First: We lead with utility. Our DeFi Learning POC is already live on YouTube. Check the site for our on-chain certifications—the tech speaks for itself. Stay focused on the build. 🏗️ #CryptoLwei #Solana #Algorand #DeFi

$LWEI is Live – The Official Contract Address 🛡️ The infrastructure is deployed. $LWEI is officially trading on the Solana network via @JupiterExchange Studio. Official Contract Address (CA): 7M9zHgCGZhZtoSUREAjgYMaioBBsfGPDvUP4F9Stjupx

$LWEI is Live – Technical Deployment Update 🛠️ We have successfully initialized the $LWEI market on Solana. As with any professional launch, we are currently in the propagation phase. Current Status: ✅ Contract Deployed: Verified on-chain via Jupiter Studio. ✅ Liquidity: 50% Locked for 12 months. ✅ Trust Specs: 2.5% Team Vesting active. Transparency Note: You may see a "Warning" or "Unverified" badge on some DEX scanners. This is a standard delay while we complete the Dexscreener Paid Update and metadata sync. We are actively pushing these updates now to ensure full credibility across all platforms. The code is the law—verify everything on our official site: 🌐 cryptolwei.com Don't trade the noise. Trade the infrastructure. 🏗️ #Lweicoin #Solana #Web3Builder #JupiterStudio