Arcium Docs
arcium.com@ArciumHQ
  • Documentation
  • Developers
  • Intro to Arcium
  • Installation
    • Arcup Version Manager
  • Hello World with Arcium
  • Arcium Computation Lifecycle
  • Encryption
    • Sealing aka re-encryption
  • Arcis
    • Operations
    • Types
    • Input/Output
    • Best practices
  • Invoking a Computation from your Solana program
    • Computation Definition Accounts
    • Callback Accounts
    • Callback Type Generation
  • JavaScript Client
    • Encrypting inputs
    • Tracking callbacks
  • Deployment
  • Callback Server
  • Current Limitations
  • Migrate from v0.1.x to v0.2.x
Powered by GitBook
On this page

Current Limitations

PreviousCallback ServerNextMigrate from v0.1.x to v0.2.x

Last updated 26 days ago

CtrlK

Output sizes

Outputs of encrypted instructions should be able to fit in a single solana transaction (the callback transaction), otherwise you need to setup additional infrastructure to handle transaction data handling via callback server.