aka kushti, core dev of Ergo (@ergo_platform). Cryptography, blockchain, research. Prev: Nxt,smartcontract.com,IOHK Papers coauthored: bit.ly/2v60r5l

Joined October 2009
Alex Chepurnoy retweeted
Alex Chepurnoy retweeted
Lads, soft launch today. it’s not perfect; it’s honest. every page is for builders first. i put my heart into this—now i need yours: feedback, issues, PRs, ideas. let’s make Ergo easier to build on. ergoblockchain.org $Erg #ERGO
Alex Chepurnoy retweeted
The goal has been creating a set of free (open-source, free to use and free to modify) financial tools on top of Ergo peer-to-peer network. Programmable money as a public good that becomes more powerful and composable through time.
We build the movement here: "Ergo ecosystem as a free and open financial stack movement" ergoforum.org/t/ergo-ecosyst…
10
1
48
Alex Chepurnoy retweeted
The next Ergo node release is getting AgentFi ready 👾
1
13
56
Alex Chepurnoy retweeted
$deUSD depegged and now trades around $0.05. Down 95% in two days: one of the fastest stablecoin deaths since $UST. Here’s how it unraveled. 👇
Alex Chepurnoy retweeted
Exchanges should focus on listing fundamentally strong coins projects with real use cases and powerful communities behind them. Not every hype deserves a listing. Quality > Quantity.
My article from 2017 for IOHK blog, "Centralized Cryptocurrencies", now even more relevant, sadly iohk.io/en/blog/posts/2017/0…
3
37
1
111
Alex Chepurnoy retweeted
Most stablecoins depend on market-driven mechanisms like arbitrage, over-collateralization, and liquidation rewards to hold their peg, which often succeeds in normal conditions but can collapse in high volatility or crises due to unverified assumptions about user behavior. While interesting as experiments market driven stablecoins often struggle to contain risk parameters due to unclear edge scenarios. SigUSD and Gluon, however, begin with mathematical theorems and formal verification, employing theorem provers to strictly demonstrate traits like limited price deviation and resilience to attacks prior to coding, creating a system theory that's fundamentally different from the ground up instead of fixed or patched after issues arise. By prioritizing this mathematical base, they avoid dependence on shaky market theories, changing breakdowns scenarios like those in algorithmic stablecoins (example UST) with a different level of certainty and assumptions that no other stablecoins atm provide.
Finishing testing on initial version of Basis tracker server, would be good to see contributors building agent-2-agent payments on top of it, please join TG group t.me/chaincashtalks (and Ergo devs also t.me/ErgoDevelopers )
1
12
77
Can someone explain why CEX managers first reach me then disappear after
8
26
2
145
Alex Chepurnoy retweeted
Asking for a friend…⛏️ What’s your go-to software for mining $ERG these days? Rigel? NBminer? TeamRed? Something custom? Curious what the community’s rocking before Lithos Testnet fires up. 🔥 #Ergo #Lithos #Mining #Crypto #PoW
Alex Chepurnoy retweeted
Back to basics. If you want privacy, you need to create it. Ergo Platform is an open source, license free, public monetary application network. But Privacy is a human right, and built into the core of how Ergo operates, as an option. #DiscoverErgo @ergo_platform
Stealth addresses contract (to keep recipient privacy) ergoforum.org/t/stealth-addr… , implemented in ErgoMixer desktop app
2
7
55
Alex Chepurnoy retweeted
On the Ergo forum, there are old discussions for blockchain based trustless derivatives built directly on the Ergo platform. Specifically HashrateCoin and RandomCoin. These are designed to derive emission from the blockchain state in a deterministic, trustless way, without relying on external oracles or custodians. Useful idk probably why they never went anywhere, but interesting. Maybe interesting to build post Lithos for miners.
9
54
Alex Chepurnoy retweeted
Big things in the pipeline. @RosenBridge_erg # 🌉 Rosen Bridge 🧪 Rosen Test (QA) - The final test milestone for Bitcoin Runes release is started. We hope to finish important ones and then start Bitcoin Runes deployment procedure by next week. However, this milestone is heavy and we plan to finish remaining tests by the time deployment process is done. Some notable updates (we will publish full changelog on release): - Added Bitcoin Runes chain (obviously!) - Replaced old P2P system with Rosenet - Integrated New Ergo Multisig package (aims to reduce P2P load mainly, alongside some minor bug fixes and improvements. All on code level) - Upgraded almost all services and packages to Node v22.18 🟣 On Chain Token Map - All supported tokens of the bridge is defined in a JSON structured file, named tokensMap, which is available in Contract Repository releases. This file is downloaded and used in Watcher and Guard services. Adding a new token to Rosen Bridge, requires the update in this file and then, the update by majority of watcher and guards, which may take some times . - To bypass this problem, we can write the supported tokens directly on the blockchain. We call this update On Chain Token Map. It was designed some months ago. - Such update is heavy as it affects many packages and all services. So we decided to apply it in 2 stages: 1. First, we update the TokenMap structure to support the parse of token configs from Ergo boxes and update the new version in all packages and services (But services still read the config from the tokensMap file same as before) 2. Second, we integrate the required modules to fetch Token Map config boxes and update the services to use these boxes instead of tokensMap file. - We've finally started the 2nd stage. Starting from UI apps. 💄 UI Apps Summary - Added a new extractor to fetch token map boxes to rosen-service. The MR is under review (Active Branch). - Added a callback to rosen-service to notify Rosen App when TokenMap is updated. The MR is under review (Active Branch). - Added a wrapped on TokenMap object to check its version so the latest version is always used. The MR is under review (Active Branch). 🛡️💄 @rosen-bridge/guard-app - Design of the Reprocess Requests page completed - Bitcoin Runes card added to the Network section of the Dashboard page 🌉💄 @rosen-bridge/rosen-app - Event Details page completed and prepared for production - Event List page updated to prevent duplicate events and correct timestamp ordering - Investigation in progress for SSR, caching, and upgrades to Next.js and MUI to improve performance and efficiency - Button component refactored to simplify API and remove unused props - Design initiated for displaying multiple event types (e.g., fraud events) in the Event List page - Development started on Filter utilities for API parsing and validation
5
31
2
116