Limits and defaults

Every number, cap and default the Bloxchain Platform enforces, with why each one matters and where it is explained.

Alpha · Testnet · Local-first. The Platform runs on Sepolia today. Ethereum mainnet is coming soon. The Protocol core is audited by Nethermind (NM_0828), core framework scope. Custom extensions and your own configuration are not covered by that audit.

Deploying an account

Setting	Value	Why it matters	Where
Owner	Your connected wallet, the one that sends the deploy	Controls the account and approves delayed requests. The official factory refuses any other owner	Deploy
Deploying wallet	A regular wallet (EOA), calling the factory directly	A deploy uses about 16.16M gas against a 16,777,216 per-transaction cap (EIP-7825), so a Safe or ERC-4337 account in front of the factory does not fit	Deploy
Recovery	One valid, non-zero address, different from the Owner	It is the fallback when the owner key is lost, so it cannot be the owner	Deploy
Broadcaster addresses	1 to 3, each unique	Separates authorising from submitting, so a compromised broadcaster is not a compromised owner	Security
Time lock	1 day to 90 days on the official factory (Minutes, Hours or Days)	Zero would remove the cancel window	Security
Address	Predictable: salt 0 and the next free index for your wallet	The same wallet, index and salt give the same address on every catalog network	Deployment
Shell	Base (the official mint deploys Base); Web3 only on a custom network whose factory offers it, with a time lock of at least 1 day	Web3 lets external apps verify signatures from the account (EIP-1271)	Deploy

Time lock

Thing	Value	Why it matters	Where
Minimum	Greater than zero, always	Validation blocks any deploy or change that sets zero	Security
BasicAccount range	1 day to 90 days	Accounts from the official factory accept nothing outside it. The Sepolia developer toolkit (AccountBlox) allows from 1 second	Deployment
Web3 shell minimum	1 day	Set at deploy under Advanced; it constrains later changes too	Deploy
Ownership transfer wait	Your current time lock	Transfer ownership is a delayed request, cancellable while it waits	Security
A change takes effect	On requests made after it	Requests already waiting keep the delay they started with	Security

Roles, signers and gates

Thing	Value	Why it matters	Where
Protected roles	Three, fixed at deploy: Owner, Broadcaster, Recovery	They are protocol security roles, not app permission roles	Roles
Custom roles	Each sets Max wallets when created	A role at its limit takes no further signer until you raise it	Roles
Gates	Permanent for that role	Only deleting a custom role clears its gates; system-role gates stay on	Gates

Actions installed at deploy

Every account registers thirty function schemas at deploy, grouped under ten operation names. You do not register these yourself; Add action is for functions of your own.

Five of the ten are the transfer and controller operations below, and they are what the Actions page shows: the operation name in upper case with the function signature underneath. The other five configure the account itself and appear on their own pages instead: OWNERSHIP_TRANSFER, BROADCASTER_UPDATE, RECOVERY_UPDATE and TIMELOCK_UPDATE on Security, and ROLE_CONFIG_BATCH on Roles.

Operation name	Function signature	Functions	Where
NATIVE_TRANSFER	__bloxchain_native_transfer__()	1	Actions
ERC20_TRANSFER	transfer(address,uint256)	1	Actions
ATTACHED_PAYMENT_RECIPIENT	__bloxchain_attached_payment_recipient__()	1	Allowlists
CONTROLLER_OPERATION	executeWithTimeLock(address,uint256,bytes4,bytes,uint256,bytes32) (entry point)	7	Allowlisted contract calls
CONTROLLER_CONFIG_BATCH	executeGuardConfigBatch((uint8,bytes)[])	2	Actions

A function selector is the first four bytes of the keccak-256 hash of the signature, identical on every network and derivable from the signature above, so it is not listed here. A future contract release that changes a signature changes its selector with it.

Thing	Value	Why it matters	Where
Schemas registered at deploy	30, under 10 operation names	A new account can already describe a transfer; what it lacks is permissions and allowlist entries	Actions
Built-in schemas	Protected: they cannot be removed or redefined	Remove action applies to functions you added	Actions
Non-revocable grants	27 of the 30 schemas	Everything except NATIVE_TRANSFER, ERC20_TRANSFER and ATTACHED_PAYMENT_RECIPIENT. A grant on any of the 27 is a permanent grant; only deleting the custom role withdraws it	Actions
A fresh account	Reads Flow incomplete on every row	The Vault state: registered but not permitted	Actions

Requests, allowlists and gas

Thing	Value	Why it matters	Where
Signed meta-transaction expiry	Shown when you sign, for example "Meta-tx expires in 1h"	After it passes, the signature is worthless and must be redone	New request
Delayed request expiry	None; it waits for approval or cancellation	A delayed request will not lapse on its own	Approvals
Allowlist entries	No published maximum; edits collect into one signed batch	An empty list allows nothing, so an unconfigured action is denied	Allowlists
Gas	Paid by the wallet that submits: requester, approver or broadcaster	No hidden relay unless you use the optional Bloxchain broadcaster	Connect a wallet

Networks and official addresses

Thing	Value	Why it matters	Where
Supported network	Sepolia, chain 11155111	The network the Platform runs on today	Supported networks
Ethereum mainnet	Chain 1, coming soon	Use test funds until it opens	Supported networks
Custom EVM networks	You add them in Settings → Networks	No official Protocol addresses; you supply them	Networks
BasicFactory (official factory)	0x6b6e4fb86ab52728d983d1a316ad9d8b48513215	Clones and initialises an account in one transaction	Deployment
BasicAccount (account template)	0x234c0a76399456832a74fb29de3c78d13c22e182	Every account from the official factory is a clone of it	Deployment
EngineBlox	0xb1fde79830ee7f748022922d07b3f19042ee6526	The shared state machine library, linked into BasicAccount	Deployment
SecureOwnableDefinitions	0xeb6ca70bb64d1f87bb708460868c9b19f6987ed6	Definitions for owner, recovery and time lock changes	Deployment
RuntimeRBACDefinitions	0x55ff61c065025e4a521532f1366981805230f988	Definitions for role configuration	Deployment
GuardControllerDefinitions	0x8e8f6c8a11161214fdf04c702981bcd8b78f2fe0	Definitions for guard and allowlist configuration	Deployment
CopyBlox (Sepolia developer toolkit)	0x928a2bd6c13e4f48a0850d2171a8d79b29959fc7	Open factory for experiments, Sepolia only. Not offered in the Platform deploy dialog	Deployment
AccountBlox (Sepolia developer toolkit)	0x783eb64d7d5de55f6913f9cb42ef5a4c402884c0	Template for experiments, Sepolia only; time lock from 1 second	Deployment
Account link shape	https://bloxchain.app/workspace/<chainId>/<address>	Read-only for anyone; acting needs a wallet holding a role	Open and share

The BasicFactory, BasicAccount, EngineBlox and definition library addresses are the same on every network in the published address catalog. The CopyBlox and AccountBlox rows are Sepolia only. All of them ship in @bloxchain/contracts as official-deployed-addresses.json; read them from that file rather than copying them into code or environment variables. See Releases and compatibility for package versions.

Stored on this device

Thing	Value	Why it matters	Where
Accounts kept in one browser	200	The same limit applies to a backup file	Backup
Custom networks kept in one browser	50	Cleared with site data, so export a backup	Networks
Backup file size on import	4 MB	A larger file is refused with "File too large"	Backup

Sign-in, plans and organizations

Thing	Value	Why it matters	Where
Free	No account needed, open to everyone	The whole operating surface works signed out	Free, sign-in and organizations
Sign in	Live for people who already have early access; everyone else joins the waitlist from the same dialog	The Free path loses nothing meanwhile	Free, sign-in and organizations
Plans	Free, Pro, Team, Enterprise	Sign-in is an identity, not a plan. Pricing is shown at checkout or on request; Enterprise is contact us	Organizations and billing
Organization before checkout	Checkout required, and it shows no accounts	Not the same as Free	Organizations and billing
Watched addresses and alerts	Organizations on Pro and above only; follows and alerts per month capped per organization; Ethereum and Arbitrum One only	The cap is shared by all members. The page shows "Alert limit reached" at the cap	Profile, notifications and privacy
Reference prices	Resolve on Ethereum and Arbitrum One only	Everywhere else, Sepolia included, the Value column shows a dash	Assets

Related

• FAQ
• Glossary
• Troubleshooting
• Known limitations