Rules, terms, restrictions and licensing

A dated research snapshot

We checked the sources for this chapter on 17 Sept 2026. Use the linked sources for current availability, terms and network details. See subsequent updates

The current network terms were updated September 16, 2026. They distinguish open application access from permissioned validation, require users to comply with applicable restrictions and place responsibility for AI-agent actions on the user. They discuss USDC issuer actions, deny lists, public and persistent onchain data, and the separation between network software and regulated financial services. S074

This is more nuanced than “permissionless means no rules.” A smart contract can be publicly deployable while a front end, financial asset, issuer, validator or company-operated API has eligibility conditions. Conversely, a service-level restriction is not automatically evidence that the company can reverse already finalized ledger history.

SurfaceWhy it mattersPrimary link
Arc network and testnetMainnet/testnet entity, usage obligations, node operators, gas, dispute termsS074
Arc PortalInterface access, supported workflows and agent responsibilityS075
OnrampThird-party onboarding/KYC, geography, fees and provider termsS076
Arc StudioSoftware service terms; incorporation of developer termsS077
USDCIssuance, redemption and issuer-control conditionsS088
Privacy policyCompany data handling and telemetryS089
Grants / Architects / bountyProgram-specific conditions, eligibility and reward rightsS043 S070 S021
Source codeApache-2.0 licenses in core repositoriesS017 S018

Portal and onramp access should not be confused with eligibility to buy every tokenized security or fund. A software API does not grant a financial license. Product-specific KYC, allowlisting, minimums and residency conditions must be checked separately. S075 S076 S090

The terms include dispute-resolution provisions and limitations of liability. These should be read in full rather than reduced to a universal statement about enforceability in every jurisdiction. Source-code licensing also does not automatically confer trademark rights or permission to claim Circle endorsement. S074 S017

Builder consequence: maintain a product-level permissions matrix covering user location, asset eligibility, transaction type, custody arrangement, API terms and autonomous-agent spending policies. It is possible to deploy technically while still failing a product's issuer or service requirements.

Sources & references

Documents cited in this chapter.

  1. Arc network termsdocs.arc.io
  2. Arc Portal termsarc.io
  3. Arc onramp termsarc.io
  4. Arc Studio termsstudio.arc.io
  5. USDC legal termscircle.com
  6. Circle privacy policycircle.com
  7. Circle developer grants programcircle.com
  8. Architect terms and conditionscommunity.arc.io
  9. Arc HackerOne programhackerone.com
  10. Arc node repositorygithub.com
  11. Malachite repositorygithub.com
  12. Circle developer documentationdevelopers.circle.com
  13. Original sourcegist.github.com