Product policy

The tables on this page read the generated policy used by the current build. They separate icLens product deductions from the network and ledger costs of executing an operation.

Policy iclens-product-policy, revision 2.

Feature behavior

Feature	Availability	Product deduction	Behavior
`manualCanisterFunding`	enabled	none	A connected wallet sends assets directly to the official ICP protocol path for the selected canister.
`automationReserveFunding`	enabled	none	A connected wallet sends assets directly to the Agent-owned Automation Reserve or its CMC account.
`automaticCanisterFunding`	enabled	none	The Agent sends cycles directly from its Automation Reserve to an eligible controlled canister.
`canisterCreationFunding`	enabled	none	OISY pays the official protocol path while the signed-in Internet Identity remains a controller of the new canister.
`agentCreationFunding`	enabled	none	OISY funds creation and the signed-in Internet Identity owns the Agent bootstrap and recovery lifecycle.

Funding units and review

ICP amounts use e8s: 100,000,000 e8s equals 1 ICP. Cycles amounts are whole cycles; 1,000,000,000,000 cycles is 1T cycles. Review expiry is expressed in nanoseconds. Keep these integers exact in integrations.

Manual funding and creation have no icLens upper amount cap, on local or mainnet. The selected wallet must cover the amount plus the current protocol costs. Ledger and canister protocol constraints still apply. Minimums apply to the named flow, and Agent creation has its own defaults. A default is a starting amount, not a guarantee of sufficient long-term funding. Automatic spending remains subject to the Agent’s configured reserve floor and spending limits.

Exact current limits

Limit	Exact value
`reviewTtlNanos`	`600000000000`
`minimumIcpE8s`	`10000000`
`minimumCycles`	`500000000000`
`minimumCreationIcpE8s`	`10000000`
`minimumCreationCycles`	`500000000000`
`defaultAgentCreationIcpE8s`	`500000000`
`defaultAgentCreationCycles`	`20000000000000`
`maximumPendingOisyOperations`	`24`
`maximumCmcProcessingAttempts`	`3`
`maximumRetainedFundingIntents`	`10000`
`maximumRetainedAutomaticTopUps`	`20000`
`maximumPageSize`	`100`
`ledgerVerificationPageSize`	`100`
`maximumLedgerVerificationPagesPerCall`	`4`
`maximumCertifiedTipBytes`	`65536`
`maximumCertifiedTreeDepth`	`64`
`maximumCertifiedIndexBytes`	`16`
`defaultAutomationReserveFloorCycles`	`1000000000000`
`defaultAutomaticDebitPer24hCycles`	`100000000000000`

Page and verification bounds limit work per request. Exhausting a verification budget does not authorize another payment: retain the original receipt and continue the supported reconciliation workflow.

Policy identity

The generated source is config/product-policy.json. Its SHA-256 is 9ecbf9fe12feb324875bca55a81eb28d353ac94aee44013852252c6e4fd619c9.

Download the policy JSON for the exact structured values. Maintainers validate generated consumers with npm run check. Operators should use direct funding or automation reserve funding for the corresponding reviewed workflow.