I don't know whether AI will replace human programmers. But I know that when you die, you will meet Dijkstra, and He will not smile upon the ungrammatical prompt that you wrote to vibe an incorrect sort function with 300 unit tests locking in the logical errors for all eternity.
@novahodler@dfinity@LiquidiumFi Hey Mo, these are normal ICRC1 addresses, you can find a breakdown here: https://t.co/AyaAEqL3IR
Also, this is not your address, this is an externally controlled canister + subaccount 😉
We've released more bug fixes and UI improvements in the past month than ever before.
It's all thanks to an agentic workflow we built based on our old purely human-driven processes.
If you use https://t.co/AMIEKCewsW or https://t.co/hcHzfG3vPa, submit more requests! If they're actionable they'll probably be done in a week.
Hey IC devs 👋
Wondering how the upcoming 2.5x protocol memory cost changes will affect your cycle bill?
We were curious too! 😅
So we built a dedicated memory cost change dashboard so that you can use to quickly understand and plan for the before and after cost impact. 🔥
🧵
New art project.
Train and inference GPT in 243 lines of pure, dependency-free Python. This is the *full* algorithmic content of what is needed. Everything else is just for efficiency. I cannot simplify this any further.
https://t.co/HmiRrQugnP
@mosesibb@WaterNeuron Small corrections:
- reaches *40m
- 100% of the (currently) 8yr neuron, not all revenue.
You can play around with the numbers here: https://t.co/0RTA0DwC79
Security Advisory: Phishing risk in SIW-E/B/S implementations 🛡️
A security advisory has been released regarding the IC-SIW* (Ethereum, Bitcoin, Solana) login flows.
🔹 Issue: These implementations are prone to phishing because they map a wallet address to an ICP principal regardless of which website requested the sign-in.
⚠️ Risk: An attacker using a malicious domain (e.g., https://t.co/wkwdPgqKCh) could trick a user into signing in and obtain a delegation to control the user's IC principal and funds.
The advisory suggests hardening security through three possible approaches:
▶️ Verifying app origin in the wallet (requires SIW* standard support).
▶️ Using passkeys as a second factor for privileged operations.
▶️ Implementing the ICRC-21 call consent messages standard for transaction-level authorization.
👇 Read the full advisory and risk analysis: https://t.co/uW7MxTwaA2
@WaterNeuron burns ~12T cycles/DAY (~$17.5), which is around ~6.4K $/YEAR. Increasing the cycle cost 5x seems really excessive and not very competitive.
Running a DAO will just become really expensive. You can find some stats provided by @CycleOps here: https://t.co/cl7S3PqFg4
UPDATED Mission 70 white paper — proposing to 5X the cost of ICP's onchain compute as provided sovereign cloud will remain very competitive.
↗️↗️↗️ Caffeine & cloud engine demand
↗️↗️ cost of onchain compute
↙️ inflation (gov + nodes)
🔥 huge deflation
https://t.co/T6HiI2wSUY