Home

Blog

About us

Home

Blog

About us

Programmable authorization for money, agents, and access

On-chain logic enforces spending limits, payments, and permissions without custody, cron jobs, or repeated signatures.

Read the Docs

Non-custodial. Time-bound. Deterministically enforced on-chain.

Time-Bound Delegation

Users authorize spending and access with strict time and amount limits. Funds always remain in-wallet and fully revocable.

Time-Bound Delegation

Users authorize spending and access with strict time and amount limits. Funds always remain in-wallet and fully revocable.

Time-Bound Delegation

Users authorize spending and access with strict time and amount limits. Funds always remain in-wallet and fully revocable.

Time-Bound Delegation

Users authorize spending and access with strict time and amount limits. Funds always remain in-wallet and fully revocable.

Deterministic Execution Windows

Transactions execute only within predefined windows — enforced on-chain, without cron jobs or race conditions.

Deterministic Execution Windows

Transactions execute only within predefined windows — enforced on-chain, without cron jobs or race conditions.

Deterministic Automation

Keeper nodes trigger charges on-chain, ensuring reliability without central servers.

Deterministic Execution Windows

Transactions execute only within predefined windows — enforced on-chain, without cron jobs or race conditions.

Idempotent Execution

Each execution window is enforced exactly once. No double-execution. No ambiguity.

Idempotent Execution

Each execution window is enforced exactly once. No double-execution. No ambiguity.

Transparent Fee Split

Every transaction distributes fees instantly to merchants, keepers, and treasury.

Idempotent Execution

Each execution window is enforced exactly once. No double-execution. No ambiguity.

Chain-Local, Multi-Chain Ready

Execution is local to each chain, while authorization remains consistent across networks.

Chain-Local, Multi-Chain Ready

Execution is local to each chain, while authorization remains consistent across networks.

Cross-Chain Future

Designed for multi-chain expansion — one protocol, many execution layers.

Chain-Local, Multi-Chain Ready

Execution is local to each chain, while authorization remains consistent across networks.

Authorize rules, not transactions

Smart contracts can enforce rules — but they can’t express ongoing authorization.

Web3 has no native way to grant permission once, define its lifetime, and enforce it automatically over time.

Amser separates authorization from execution, allowing users to approve rules up front — and smart contracts to enforce them later, deterministically and on-chain.

Web3 still lacks a native standard for automated payments.

SubNetwork introduces an open, non-custodial protocol for recurring billing and automated payments — built for merchants, developers, and keeper operators.

Bridging Web2 simplicity with Web3 sovereignty, it brings familiar recurring payment experiences to a decentralized world — trustless, user-controlled, and seamless.

Define Authority

Merchants define rules, not transactions.

Configure recurring payment and access rules with transparent on-chain logic — no intermediaries, no custodial risk.

Define Authority

Merchants define rules, not transactions.

Configure recurring payment and access rules with transparent on-chain logic — no intermediaries, no custodial risk.

Define Authority

Merchants define rules, not transactions.

Configure recurring payment and access rules with transparent on-chain logic — no intermediaries, no custodial risk.

Define Authority

Merchants define rules, not transactions.

Configure recurring payment and access rules with transparent on-chain logic — no intermediaries, no custodial risk.

Grant Time-Bound Permission

Users authorize rules — with strict time and amount limits.

Subscribers approve spending and access once through a secure delegation model. Funds stay in their wallet, permissions are bounded, and authority is always revocable.

Grant Time-Bound Permission

Users authorize rules — with strict time and amount limits.

Subscribers approve spending and access once through a secure delegation model. Funds stay in their wallet, permissions are bounded, and authority is always revocable.

Grant Time-Bound Permission

Users authorize rules — with strict time and amount limits.

Subscribers approve spending and access once through a secure delegation model. Funds stay in their wallet, permissions are bounded, and authority is always revocable.

Grant Time-Bound Permission

Users authorize rules — with strict time and amount limits.

Subscribers approve spending and access once through a secure delegation model. Funds stay in their wallet, permissions are bounded, and authority is always revocable.

Enforce Over Time

Execution happens automatically when conditions are met.

Actions execute deterministically within predefined windows. Each execution is enforced exactly once — transparent, verifiable, and on-chain.

Enforce Over Time

Execution happens automatically when conditions are met.

Actions execute deterministically within predefined windows. Each execution is enforced exactly once — transparent, verifiable, and on-chain.

Enforce Over Time

Execution happens automatically when conditions are met.

Actions execute deterministically within predefined windows. Each execution is enforced exactly once — transparent, verifiable, and on-chain.

Enforce Over Time

Execution happens automatically when conditions are met.

Actions execute deterministically within predefined windows. Each execution is enforced exactly once — transparent, verifiable, and on-chain.

Authorization and execution are no longer the same action.

More than subscriptions

Subscriptions are just one expression of programmable authorization. The same execution model powers many transaction patterns.

Recurring access enforced through time-bound authorization.
Users approve rules once, and execution happens automatically at each interval — without repeated signatures.

Subscriptions & memberships

Recurring access to products, protocols, or services — enforced automatically over time.

Usage-based billing

Metered execution that runs within predefined limits, without repeated user signatures.

API & SaaS access

Time-bound authorization backing on-chain and off-chain services with expiring permissions.

Autonomous agents

Agents that operate continuously with safe, delegated authority and strict execution rules.

Smart contract access control

Gate functions, features, or mints based on active authorization state.

Protocol infrastructure fees

Automated fees that execute predictably without manual intervention or cron jobs.

All powered by the same primitive: authorize rules once, enforce them over time.

More than subscriptions

Subscriptions are just one expression of programmable authorization. The same execution model powers many transaction patterns.

Recurring access enforced through time-bound authorization.
Users approve rules once, and execution happens automatically at each interval — without repeated signatures.

Subscriptions & memberships

Recurring access to products, protocols, or services — enforced automatically over time.

Smart contract access control

Gate functions, features, or mints based on active authorization state.

Autonomous agents

Agents that operate continuously with safe, delegated authority and strict execution rules.

Protocol infrastructure fees

Automated fees that execute predictably without manual intervention or cron jobs.

API & SaaS access

Time-bound authorization backing on-chain and off-chain services with expiring permissions.

Usage-based billing

Metered execution that runs within predefined limits, without repeated user signatures.

All powered by the same primitive: authorize rules once, enforce them over time.

More than subscriptions

Subscriptions are just one expression of programmable authorization. The same execution model powers many transaction patterns.

Subscriptions & memberships

Recurring access to products, protocols, or services — enforced automatically over time.

Usage-based billing

Metered execution that runs within predefined limits, without repeated user signatures.

API & SaaS access

Time-bound authorization backing on-chain and off-chain services with expiring permissions.

Autonomous agents

Agents that operate continuously with safe, delegated authority and strict execution rules.

Smart contract access control

Gate functions, features, or mints based on active authorization state.

Protocol infrastructure fees

Automated fees that execute predictably without manual intervention or cron jobs.

All powered by the same primitive: authorize rules once, enforce them over time.

More than subscriptions

Subscriptions are just one expression of programmable authorization. The same execution model powers many transaction patterns.

Recurring access enforced through time-bound authorization.
Users approve rules once, and execution happens automatically at each interval — without repeated signatures.

Subscriptions & memberships

Recurring access to products, protocols, or services — enforced automatically over time.

Usage-based billing

Metered execution that runs within predefined limits, without repeated user signatures.

API & SaaS access

Time-bound authorization backing on-chain and off-chain services with expiring permissions.

Autonomous agents

Agents that operate continuously with safe, delegated authority and strict execution rules.

Smart contract access control

Gate functions, features, or mints based on active authorization state.

Protocol infrastructure fees

Automated fees that execute predictably without manual intervention or cron jobs.

All powered by the same primitive: authorize rules once, enforce them over time.

Protocol guarantees

Amser is designed around strict, enforceable guarantees.
These are not conventions — they are properties of the protocol.

Transparent and verifiable

All authorization and execution logic lives on-chain. Anyone can verify what is allowed, when it executes, and why.

Transparent and verifiable

All authorization and execution logic lives on-chain. Anyone can verify what is allowed, when it executes, and why.

Deterministic execution

Actions execute only when predefined conditions are met. Execution may be attempted multiple times, but can only succeed once, and only within valid execution windows — deterministic and on-chain.

Deterministic execution

Actions execute only when predefined conditions are met. Execution may be attempted multiple times, but can only succeed once, and only within valid execution windows — deterministic and on-chain.

Transparent and verifiable

All authorization and execution logic lives on-chain. Anyone can verify what is allowed, when it executes, and why.

Transparent and verifiable

All authorization and execution logic lives on-chain. Anyone can verify what is allowed, when it executes, and why.

Deterministic execution

Actions execute only when predefined conditions are met. Execution may be attempted multiple times, but can only succeed once, and only within valid execution windows — deterministic and on-chain.

Deterministic execution

Actions execute only when predefined conditions are met. Execution may be attempted multiple times, but can only succeed once, and only within valid execution windows — deterministic and on-chain.

Non-custodial by design

Funds never leave the user’s wallet. Authorization grants permission — not custody — and can be revoked at any time.

Non-custodial by design

Funds never leave the user’s wallet. Authorization grants permission — not custody — and can be revoked at any time.

Non-custodial by design

Funds never leave the user’s wallet. Authorization grants permission — not custody — and can be revoked at any time.

Time-bound authorization

Every authorization has explicit start and end conditions. Permissions expire automatically — no lingering approval

Time-bound authorization

Every authorization has explicit start and end conditions. Permissions expire automatically — no lingering approval

Time-bound authorization

Every authorization has explicit start and end conditions. Permissions expire automatically — no lingering approval

Deterministic execution

Actions execute only when predefined conditions are met. Execution may be attempted multiple times, but can only succeed once, and only within valid execution windows — deterministic and on-chain.

Deterministic execution

Actions execute only when predefined conditions are met. Execution may be attempted multiple times, but can only succeed once, and only within valid execution windows — deterministic and on-chain.

Deterministic execution

Actions execute only when predefined conditions are met. Execution may be attempted multiple times, but can only succeed once, and only within valid execution windows — deterministic and on-chain.

Transparent and verifiable

All authorization and execution logic lives on-chain. Anyone can verify what is allowed, when it executes, and why.

Transparent and verifiable

All authorization and execution logic lives on-chain. Anyone can verify what is allowed, when it executes, and why.

Transparent and verifiable

All authorization and execution logic lives on-chain. Anyone can verify what is allowed, when it executes, and why.

These guarantees apply to every execution — without exception.

Built for developers

Amser is designed to be predictable to build on.
The execution model is explicit, inspectable, and consistent under real-world conditions.

Clear, composable primitives — no hidden flows or implicit behavior
Predictable behavior under retries, failures, and edge cases
On-chain authority with off-chain liveness assistance

Clear, composable primitives — no hidden flows or implicit behavior
Predictable behavior under retries, failures, and edge cases
On-chain authority with off-chain liveness assistance

Clear, composable primitives — no hidden flows or implicit behavior
Predictable behavior under retries, failures, and edge cases
On-chain authority with off-chain liveness assistance

Developers can rely on this behavior across all execution paths.

Email Address

hello@amser.io

Social Media