%20scale(.8)'%3e%3cpath%20d='M116.770%2049.147A48%2048%200%201%200%20116.770%20110.853'%20fill='none'%20stroke='%2316263D'%20stroke-width='27.5'%20stroke-linecap='round'/%3e%3cpath%20d='M138.5%2080%20A10.5%2010.5%200%201%200%20117.5%2080%20A10.5%2010.5%200%201%200%20138.5%2080%20Z'%20fill='%23F06D5E'/%3e%3c/g%3e%3cg%20fill='%233D8B83'%20stroke='%233D8B83'%20stroke-linecap='round'%20stroke-linejoin='round'%3e%3cpath%20d='M445.5%20132%20A7.5%207.5%200%201%200%20430.5%20132%20A7.5%207.5%200%201%200%20445.5%20132%20Z'%20stroke='none'/%3e%3cpath%20d='M511.5%20110A25.5%2025.5%200%201%201%20486%2084.5A25.5%2025.5%200%200%201%20511.5%20110V135.5'%20fill='none'%20stroke-width='14'/%3e%3cpath%20d='M552%2091V135.5'%20fill='none'%20stroke-width='14'/%3e%3cpath%20d='M559.5%2068%20A7.5%207.5%200%201%200%20544.5%2068%20A7.5%207.5%200%201%200%20559.5%2068%20Z'%20stroke='none'/%3e%3c/g%3e%3c/svg%3e)
Connect real-world requests to verifiable outcomes.
The whitepaper brings protocol architecture, user authority, Nodes and evidence, settlement boundaries, and roadmap evidence into one reading flow.
IROA NETWORK ATLAS
A verifiable execution network for the real world.
IROA is a protocol direction that coordinates user-approved real-world tasks through AI, people, institutions, and request-specific verified Nodes—through to a confirmed outcome.
Explore the network
- 01Voice Request
- 02Task Capsule
- 03Verified NodeN2
- 04Proof Receipt
- 05Base SettlementNative USDC · Planned
- 01Interaction Plane
- 02Control Plane
- 03Execution Plane
- 04Settlement Plane
- User-controlled approval
- Data minimization
- Outcome verification
- Base Primary NetworkPlanned
- Native USDC SettlementPlanned
- Personal Data Off-chain
- IROA Rewards · In Validation
FOUR OPERATING PLANES
Four planes connect human intent to real-world outcomes.
Each plane has a distinct role. IROA never presents an external service’s authority or outcome as its own.
01
Interaction Plane
Captures user intent and approval through phone, watch, mobile, kiosk, and companion devices.
In validation02
Control Plane
Separates request state, consent, policy, and trust levels.
In validation03
Execution Plane
Runs an isolated Task Capsule with minimum permissions and cleans up when it ends.
In validation04
Settlement Plane
Explores a future B2B settlement boundary based on verified completion evidence.
Planned
Network Atlas
IROA Protocol Path
Requests execute with bounded authority, pass through verifiable outcomes, and reach a planned settlement boundary.
Stage 01
Request
The user states a goal by voice, text, or touch and directly approves every consequential action.
User approval point
Consequential actions advance only after the user confirms them.
Stage 02
Task Capsule
Purpose, one-time permission, data class, expiry, and confirmation points are bound to each request.
- Purpose
- Execute the approved request
- Permission
- One-time permission within request scope
- Data class
- D2
- Duration
- Until completion or expiry
- Public status
- In validation
Stage 03
Verified Node
A Node with the required trust level and verified runtime performs only the bounded task.
N2 Node
In validationAn example verification stage that checks policy and runtime state.
Stage 04
Proof Receipt
External outcomes and policy requirements are checked, leaving only the minimum evidence required.
- Outcome
- Verifiable outcome summary
- Proof ID
- No live transaction identifier published
- Policy baseline
- Published whitepaper baseline
- Dispute state
- Validation process in design
Stage 05
Base Settlement
A future B2B settlement direction, subject to deployment, legal, and security review.
- Network
- Base
- Settlement asset
- Circle Native USDC
- Public status
- Planned
A future B2B settlement direction, subject to deployment, legal, and security review.
NODE & PROOF
Nodes and evidence have separate, verifiable roles.
No Node controls the entire request. User approval, bounded authority, and external outcome checks remain distinct boundaries.
01 / VERIFIED NODE
N2 Node
In validationN2 is the design and review stage for approved access points such as kiosks, welfare centers, and companion devices.
02 / PROOF RECEIPT
- Outcome
- A task is not complete until its external outcome is verified.
- Proof ID
- Proof identifiers are published only when deployment and operation can support the claim.
- Policy baseline
- Policy version is kept as separate minimum evidence.
- Dispute state
- Uncertain outcomes move to human review and dispute handling.
Privacy Boundary
Keep minimum evidence, not raw data.
Raw personal data remains off-chain.
- Minimum on-chain evidence
- Policy version
- Outcome-integrity hash
- Minimal settlement proof separated from identity
- Protected off-chain area
- Raw personal data
- Conversation, health, and booking details
- Passwords, OTPs, and payment keys
SETTLEMENT BOUNDARY
Consumer payment and B2B settlement remain separate.
Base and Circle Native USDC are a future B2B settlement direction, subject to deployment, legal, security, and completion-evidence reviews. They are not live settlement infrastructure.
Consumers use KRW, cards, bank transfers, and established payment channels.
- 01Consumer payment
KRW · card · bank transfer · existing payment channels
- 02Request and approval
Confirm scope, cost, and permission
- 03Outcome check
Check external outcome and dispute state
- 04B2B settlement
Base · Circle Native USDC · planned
- Network
- Base
- Settlement asset
- Circle Native USDC
- Public status
- Planned
A future B2B settlement direction, subject to deployment, legal, and security review.
- Gas and wallet management are not consumer requirements.
- IROA will not issue its own stablecoin initially.
- Raw personal data and detailed execution records are not placed on-chain.
ECONOMY STATUS
Reward design begins with service sustainability.
IROA explores rewards for verified execution, accessibility quality, security, and deletion compliance. Access to essential support never depends on token ownership.
IROA Rewards
In validationIROA Rewards remain in validation until issuance, legal review, deployment, and audit evidence are complete.- No promise of price, yield, liquidity, or exchange listing.
- Verified contribution is evaluated together with dispute, cancellation, and quality rules.
- Token ownership is not a condition for essential daily support.
WEB WHITEPAPER
IROA.AI Whitepaper
The complete English edition of the IROA.AI whitepaper. The Korean edition remains the controlling version.
- Version
- v1.0
- Controlling language
- Korean Master
- Publication status
- Current
EVIDENCE-GATED ROADMAP
Entry criteria and evidence matter more than dates.
Each phase shows its status, entry criteria, and required evidence so plans are never presented as live operations.
- 01
Foundation
CurrentPublish the whitepaper and shared principles, and fix the public status language for each capability.
- Entry criteria
- Public information separates operational evidence from plans.
- Evidence
- Whitepaper v1.0 and published design principles
- 02
Request Validation
NextValidate bounded requests that require approval, recovery, and human handoff.
- Entry criteria
- Users understand and can confirm goals and outcomes.
- Evidence
- Request lifecycle and field-validation criteria
- 03
Secure Execution
PlannedDesign and review per-request isolation, one-time permission, and deletion confirmation.
- Entry criteria
- Residual sensitive data and duplicate execution are controlled.
- Evidence
- Task Capsule and secure execution principles
- 04
Network Research
Long-term researchLong-term research on institutional links, execution-space rewards, companion devices, and high-risk robotics.
- Entry criteria
- Legal, safety, and field evidence comes first.
- Evidence
- Node trust levels and staged safety review
INSTITUTIONAL READINESS
Design the validation scope with institutions and practitioners.
Future participation begins with the target users, one real-world task, and the current failure, delay, and human-handoff process.
Official contact channel in preparation