DeFi data is becoming a lot more than just BTC/USD or token prices.
As more assets move on-chain and new vaults, markets, and tokenized assets emerge, the need for reliable, curated data becomes even more important.
The next phase of DeFi needs better data infrastructure.
@OasisProtocol oasis-network:native
1/
Most onchain processes are public while they are still open.
A vote.
A bid.
A trade.
A strategy.
Anyone can see who is participating, which way they lean, and how much weight they carry. A process you can watch halfway through tends to steer the second half.
@OasisProtocol
8/
A short question for any process that matters:
Can other people see the intermediate moves before it finishes, and does that change what people do?
If the answer is yes, the result is already being steered.
https://t.co/xyGDL9nKec
@OasisProtocol
In the Paul Barron interview, Concordium’s CEO separates two problems that are easy to treat as one.
Agents can already discover a service and pay for it over x402. That is an engineering problem, and several payment rails are solving it. What a completed payment does not show is who authorised the agent or who answers if the order is wrong. That is a trust problem.
Visa’s observation, raised in the conversation, is that the industry still has not figured out agent identity. Concordium’s position is that the check has to sit at the protocol level: every registered agent is linked to a verified person or business, a counterparty can confirm the link on-chain, and the owner’s personal data stays off-chain. The badge means accountable, not endorsed. It does not review the agent’s code.
The agent does not have to move to get the check. It keeps its wallet and its payments where they already are. Only the proof of an owner is added.
Full episode: https://t.co/NjsHdmeqRM
@Concordium $CCD
The next big opportunities shouldn't be out of reach.
@IPOGenie is exploring how AI-powered intelligence and blockchain technology can open new possibilities in pre-IPO markets.
Bringing private-market opportunities closer to the onchain economy.
Join us today: https://t.co/DwlYk1hFmz
In the Paul Barron interview, Concordium’s CEO draws a simple line: agents can already pay for anything with x402, but nobody knows who is behind them.
That is the problem the episode focuses on. Payment rails are shipping. What institutions still lack is a way to confirm a verified person or business stands behind the agent without the owner’s personal data going on-chain. Concordium’s position is that this check belongs at the protocol level, not as an optional add-on.
The conversation also covers ERC-8004, privacy, the Mastercard partnership, and why verification has to be available before broad agent adoption, not reconstructed after something goes wrong.
Full episode: https://t.co/NjsHdmeqRM @Concordium concordium:native
AGI and, later, superintelligence raise real alignment questions.
The concerns that feel most immediate are not the distant sci-fi ones. They are the societal ones. What happens when skills that people spent the last twenty years learning no longer have a clear place, because a different kind of intelligence can do the work?
The honest answer is probably somewhere in the middle. The technology will create new uses. It will also leave gaps that policy, education, and systems design have to fill.
One practical part of that design is control. When powerful tools handle sensitive data or make decisions that affect people, the ability to verify what ran and to limit what the system can see matters more, not less.
@OasisProtocol
#PrivacyYouCanVerify #ROSE #OasisNetwork #AIPrivacy
One line from the Paul Barron interview with Concordium’s CEO stands out: Visa’s view that the industry still has not figured out agent identity.
Agents can discover services and pay. The open question is who authorised them and who answers if the payment is disputed. Boris Bohrer-Bilowitzki walks through how Concordium ties an agent to a verified person or company while keeping the owner’s identity private, and why that check has to sit at the protocol level if agents are going to be trusted with real value.
Worth a listen if you are following x402 and ERC-8004. https://t.co/NjsHdmeqRM
@Concordium@BBilowitzki@paulbarron concordium:native
“We take your privacy seriously” is still not a privacy policy.
It is a sentence. It does not tell you what the system can see while it works, how long access lasts, or whether you can check any of it. Most of the time it is the digital version of “accept all cookies”, a button people click because the alternative is slower.
A stronger standard is simpler: keep sensitive information closed during use, and let people verify what ran instead of accepting a description of it.
That is the approach @OasisProtocol is built around. Supported by $ROSE.
#PrivacyYouCanVerify #ROSE #OasisNetwork
An agent that can complete a payment can still be nobody’s agent.
The payment shows funds moved. It does not show who authorised the agent or who answers if the order is wrong. That is the gap the Agent Registry is built for. A counterparty can check, on-chain, that a verified person or business stands behind the agent. The owner’s personal data stays off-chain. The badge means accountable, not endorsed. It does not review the agent’s code or approve its use case.
The agent does not have to move to @Concordium to get that check. It keeps its wallet and its payments where they already are. The proof of an owner is what gets added.
concordium:native
On most blockchains anyone can read any contract for free. That works when everything is public.
A confidential contract has a harder job. Before it can show a private balance, it needs to know who is asking. On Sapphire a plain read arrives with no sender, so typing someone else’s address returns nothing.
You prove who you are with a signature. The contract checks it and only then answers. Your private data goes to you and nobody else.
That is the standard @OasisProtocol is built around. Supported by oasis-network:native .
#PrivacyYouCanVerify #ROSE #OasisNetwork
concordium:native is getting more attention today, but the useful part is what people can actually check.
Town Hall #6 put the Agent Registry at 5,040 registered agents and agent-related transactions up 47 times to more than 738,000 since July. Six platforms now read the registry. Agents stay on their own chains. The Verified by Concordium badge lets a counterparty confirm a verified person or business stands behind the agent without the owner’s personal data going on-chain. It means accountable, not endorsed.
The same session announced EURQ on testnet (MiCA-licensed euro, mainnet targeted for December), 75 million concordium:native set aside for builders who make agents accountable, and Protocol-Level Locks heading to public testnet in mid-December and mainnet in January.
Agents can already pay. The layer being used is the one that answers who stands behind them.
@Concordium concordium:native
@Concordium@BBilowitzki Adoption numbers matter, but actual network activity tells a deeper story. On-chain data gives the community something concrete to evaluate.
The line that stuck: payments are an engineering problem. Identity is a trust problem.
Agents can already discover a service and pay over x402. What a bank, merchant or regulator still cannot see from that payment alone is who authorised the agent and who answers if it goes wrong.
That is the gap Concordium’s CEO walks through with @paulbarron. Verified owner at the protocol level, personal data stays off-chain, badge means accountable not endorsed.
@Concordium@BBilowitzki concordium:native
“Payments are an engineering problem. Identity is a trust problem.”
Our CEO, @BBilowitzki, joins @paulbarron to unpack one of the biggest challenges facing the agentic economy.
AI agents, x402, ERC-8004, privacy, and the role Concordium plays in bringing accountability on-chain.
🎙️ Full interview 👇
https://t.co/bMpdVo4TVW