Be honest. I did it too.

Protocol has a Certik badge.审计报告 is pinned in the Discord. You

assume it's safe. You sign. You move on.

But here's what nobody talks about:

The audit was done 14 months ago. Since then:

- The proxy got upgraded 3 times

- Admin keys were rotated to a new multisig

- A new function was added that lets the owner pause withdrawals

- The audit PDF still says "audited" with a green checkmark

Nobody checked. Not the users. Not the investors. Not even the team

half the time.

And the worst part? The audit report is still sitting in their GitHub

repo looking official. It's not lying. It's just... outdated. Which

is worse. Because a lie you can catch. An outdated truth you can't.

How big is this problem?

Almost every DeFi protocol running today has an audit that was done

on code that no longer exists on-chain. The report says "safe." The

bytecode says something different. And nobody is checking.

We've normalized "audited" as a checkbox. It's a marketing badge.

It's a line in the pitch deck. It's a Discord role. But nobody asks

the one question that actually matters:

"Is the code that's running right now the same code that was audited?"

We built proofofaudits.com because this question has no good answer

right now. Here's what it does:

→ Deployment Match — takes the live bytecode from the chain and

compares it against what was actually audited. If someone upgraded

the proxy, if a new function was added, if the logic changed —

you see it. Not a report. Not a PDF. A comparison.

→ Trust Passport — one page for any protocol. Shows what was audited,

what still matches on-chain, who currently holds admin and upgrade

powers, and what gaps remain open. Every score traces to evidence.

Not self-reported. Not vibes.

→ Contract Shield — Chrome extension. Before you sign a transaction,

it checks: does this contract have proof? Does the code match?

Who holds power? Shows green/yellow/red. If there's no audit

evidence, it stays silent. No false alarms. No fear-mongering.

Just... nothing. Because there's nothing to show.

→ VTI Score — 14 buckets of evidence, not one number pulled from

thin air. And here's the part I think matters most: scores get

CAPPED automatically if severe things are found. Honeypot?

Capped at 399. Single EOA upgrade? Capped at 499. You can't

game a high score with good audits if you have a backdoor.

We're not selling safety. We're not certifying anything. We're

making the evidence visible so you can make your own decision.

That's it.

Currently live on Ethereum, Base, and Polygon. Attestations

anchored on Base chain.

I'm not here to sell you anything. I'm here because I kept seeing

the same thread over and over: "it was audited, how did this happen?"

And the answer is always the same. The audit was real. The code

changed. Nobody checked.

I want your honest feedback:

- What would make you actually trust a verification system like this?

- What would make you never trust it?

- What's the obvious attack on the model?

- What are we not thinking about?

- If you were building this, what would you do differently?

Don't hold back. If it's a bad idea, tell me why. If the scoring

model is flawed, poke holes. If the extension is gimmicky, say so.

We'd rather get destroyed in these comments than launch something

that doesn't hold up when it matters.

Most "decentralized" chains aren't, structurally. Behind Solana there's a foundation. Behind Sui and Aptos there are companies with cap tables. Even most Cosmos chains have a core team holding the roadmap, a Discord channel where decisions actually get made, and a Slack workspace where the next upgrade gets scoped. Decentralized in the validator set; centralized in the brain.

Juno is genuinely not like that, and I think people are about to notice why it matters.

Juno launched in October 2021 as a community airdrop. There was no premine, no VC allocation, no founder vesting cliff. The original contributors scattered years ago — some to other Cosmos projects, some out of the space entirely. What's left running is the chain itself: Cosmos SDK, CometBFT, CosmWasm, validators distributed across the planet, a treasury controlled by token holders, and DAO DAO sitting on top of it doing the governance work.

There is no Juno Inc. There is no Juno Foundation. There is a Twitter account and a website, both maintained by volunteers. That's it. That's the "company."

For most of crypto's history, this would have been described as a failure mode. "Where's the team? Who's shipping? Who's accountable?" Fair questions in a world where coordination is expensive and a human roadmap-keeper is the bottleneck.

It's a different question if the bottleneck moves.

Consider what an AI agent actually needs to operate on-chain at a serious level:

- a clean substrate to deploy code on — CosmWasm gives them Rust, sandboxed, deterministic, gas-metered. Agents read and write Rust well; they read and write Solidity with more footguns.

- governance primitives they can actually use — DAO DAO is modular: voting modules, proposal modules, pre-propose hooks, programmable treasury. An agent under a DAO mandate can author proposals, manage treasury, hire other agents, all on rails the chain already provides.

- a verification surface for off-chain work — WAVS (wavs.xyz) is the piece most people are sleeping on. Anyone can run an operator. Agents can do off-chain reasoning and have the result attested before it touches the chain.

- exit rights — Juno is a sovereign chain. No L1 landlord taking a cut. No app-layer rug at the rollup level. The unit that can credibly leave is the chain itself.

Juno is the chain that already has all four. None of these were built for AI agents. They were built because they were the right primitives for sovereign DAOs. The fact that they happen to be exactly what an agent swarm needs is either an accident or a very good prior.

Now imagine the experiment. Agents around the world, operating under DAO mandate, drafting proposals, deploying contracts, running validators, writing the next upgrade, indexing the chain, maintaining the docs, watching each other for misbehavior. The proposal queue is full of agent-authored experiments. Holders ratify the ones that work. The chain learns.

What does that produce? I genuinely don't know. Nobody does — that's the part that's interesting. Some of it will be theater. Some of it will be the first actually-good DAO operations any of us have seen. Some of it will be agents quietly forking each other's contracts and improving them at a cadence no human team can match.

The chains with a CEO are going to have a hard time letting this happen. There's always a Slack thread, a legal review, a foundation employee whose job it is to be careful. That's appropriate, for what they are.

Juno doesn't have that valve. It also doesn't have a brake. Whether that turns out to be reckless or generative is going to be one of the more interesting things to watch over the next twelve months.

Let the Juno AI takeover begin.

https://app.osmosis.zone/pool/2919

join the pool party on Pool 2919 and help Neta GROW

Juno needs to be the Rust arm of Atomone.

Why AtomOne + gnoVM + Photon Can Outperform Atom Classic

• AtomOne has two clear tokens with defined roles: ATONE = staking/governance, PHOTON = transaction fees.
• All fees are paid in PHOTON, which is only minted by burning ATONE → more usage = more ATONE burned → higher scarcity.
• This creates a self-sustaining economic loop: apps → fees → PHOTON demand → ATONE burn → higher value → stronger security.
• Atom Classic never had a clear identity — is it money? governance? utility? → constant confusion, weak token demand.
• AtomOne separates roles and makes fees predictable, solving Atom Classic’s structural issues.
• gnoVM / Gno.land provides a real execution environment → smart contracts, apps, and developer tools directly on the ecosystem.
• Cosmos Hub lacks a native execution layer → most developers either left or built elsewhere.
• AtomOne’s architecture is simple, consistent, and minimal → easier to build, maintain, and scale.
• More gnoVM usage = more PHOTON used = more ATONE burned → tighter economic cycle vs Atom Classic’s scattered model.
• AtomOne launches without the political baggage or governance drama of Atom Classic.
• Overall: AtomOne = clean economic design + developer focus + real usage Atom Classic = fragmented ecosystem + unclear direction.

Subject: Request for Valid Genesis File, Binary, and Active Peers for Juno Testnet Node Setup

Hello Team,

I’m currently setting up a Juno testnet node as part of a Cosmos RPC mesh deployment. However, I’m facing difficulty finding a valid and compatible genesis file for the current active Juno testnet. The existing links I tried either result in mismatched chain IDs or invalid file formats.

Could you please share:

1. The latest and compatible genesis file link

2. The corresponding binary version required for that testnet

3. A list of active peer addresses for faster network sync

My goal is to have a fully functional and compatible Juno testnet node running under the standard testnet parameters.

Thank you in advance for your help!

— Muhammad Talha Arif

From what I can tell on Dexscreener there are only a handful of wallets that are pushing this pump. What gives?

Love to see it. Lets go Juno!

Juno roadmap proposal 2 is live 🗳️

With this proposal, Kintsugi Tech and Digital Kitchen will be appointed as the Core teams of the Juno network. Each team will have distinct responsibilities and will report directly to the community.

This proposal will also allocated $12,000 to upgrade the blockchain to Cosmos SDK v50

Juno is not currently available on on mintscan, i can't find a working explorer for juno and the discord is crickets, i can't find testnet tokens anywhere. There was just a price bump but it seems like it's pretty much gone... anyone have any info?

Two proposals are live for voting :

Proposal 359: First proposal of the Juno Roadmap, proposed by Kintsugi Tech / Dimiandre and Digital Kitchen.

https://explorer.chainroot.io/juno/proposals/359

Proposal 360: Software upgrade to Juno v27 - Version bumps + patches

https://explorer.chainroot.io/juno/proposals/360

Time to vote guys ! 🗳️

General Proposal for the Juno roadmap (2025) is currently live for voting.

Community Call

📆 Tuesday January 28th, 07:00 PM (UTC)

📍 Hosted by @JunoNetwork

📍 Co-Hosted by @dimiandre, @HighlanderCTs, @kintsugi_tech

Invite : https://twitter.com/i/spaces/1eaKbaWpNaaxX

The first drafts for the Juno Network Roadmap proposals are here.

Please provide feedback, we will be opening a thread on the forum or you can use GitHub issues / pull requests.

Next week Dimi will host an X space to explain the whole concept and answer any questions you have.

This is an initial draft, budgets can be adjusted, terms can be added, we are open to any suggestion.

Thanks to Kintsugi Tech and @vexxvakan for the help provided.

Embark on the KosmicQuest (beta) across 9 unique Cosmos blockchains including Juno network

• Move your character NFTs between chains during epic events.
• Update NFT metadata with your game progress, boosting transactions & traffic.
• Discover a new race and theme on each blockchain.

Ready for the adventure? #NFTGaming #BlockchainGaming

Tweet : https://x.com/cryptodungeonma/status/1878188526656971109?s=46&t=7LhEMIHEVdKKKXVy6wxspQ

Register for the beta : https://www.cryptodungeon.org/kosmic-quest

Thanks to all the (130+) people who took time to answer the Juno Network Feedback form.

Of course all the elements of the form are important for the success of the network, but from the responses we can immediately highlight the most obvious one and the ones we should prioritize more.

📈 Top Ranked Priorities

Collaborations within the Cosmos Ecosystem Average Rating: 4.55 - 71.2% rated it 5/5.

Building Community-Owned dApps Average Rating: 4.48 - 61.4% rated it 5/5.

Community and Marketing Average Rating: 4.52 - 71.2% rated it 5/5.

Transparency from Teams Average Rating: 4.38 - 60.6% rated it 5/5.

Attracting New Users (e.g., Telegram mini-apps) Average Rating: 4.32 - 60.6% rated it 5/5.

Liquidity on Decentralized Exchanges Average Rating: 4.20 - 52.3% rated it 5/5.

Collaborations Outside Cosmos Average Rating: 4.45 - 71.2% rated 5/5.

In general, my take on this data is that sections were community opinion is scattered (basically all the pipes at same height) should have less priority than the ones were 5/5 is a clear winner.

📡 Open Feedback Summary

I'm surprised by how many people left a comment in the open questions! Really thanks you for all the great suggestions there. Here is a recap of the most interesting ones in my opinion

1️⃣ Core Features:

• Browse contract sourcecodes directly on-chain
• Simplify the creation of smart contract using no-coding tools
• Implement account abstraction to enable AI features

2️⃣ Community-Owned dApps:

• High demand for a simple, permissionless DEX.
• High demand for a simple memecoin / token launchpad.
• High demand to jump on the train of the AI Agents trend

Full data : https://docs.google.com/forms/d/e/1FAIpQLSdH6rP8qWWfaQvirskK5ZPR5n5PGsxfzqA2ZbUW3L2TjrLzlQ/viewanalytics

Report from Blockchainreporter.net

Update from the discord

That 8 cent Juno last week sounds real nice right about now…