Alpha Vault Changelog

​

Release summary

​

What We Shipped

• Merkle Proof Metadata
• User able to withdraw extra quote token in prorata vault

​

What To Do

​

Program: alpha-vault 0.4.1

​

Changed

• Allow user to withdraw overflowed deposit (extra token required to fill vault) using withdraw endpoint right after deposit close.

​

Added

• New endpoints create_merkle_proof_metadata and close_merkle_proof_metadata, that allows vault_authority (creator) to add an url to proof, easier to integrations to get proof

​

TypeScript SDK: @meteora-ag/alpha-vault-sdk 1.1.14

​

Added

• createMerkleProofMetadata function. Allow vault creator to submit merkle proof API endpoint.
• closeMerkleProofMetadata function. Allow vault creator to close merkle proof metadata account.
• getMerkleProofUrl function. Get merkle proof API endpoint from merkle proof metadata account. If not available, it default back to meteora API endpoint
• deriveMerkleProofMetadata function. Derive merkle proof metadata account PDA.
• getMerkleProofForDeposit function. Get merkle proof required for deposit based on merkle proof API stored in MerkleProofMetadata.

​

Changed

• withdrawRemainingQuote can only be invoked after vault fill stage, which the condition is current_point > last_buying_point.
• withdraw have 2 stages now. The first stage is to withdraw from escrow and the second stage is to withdraw excessive quote token from the vault. The second stage (new stage) is only applicable when the vault is in prorata mode. The second stage is triggered when the current_point >= last_join_point && current_point <= last_buying_point. The second stage is being represented as canWithdrawDepositOverflow in InteractionState object, and the amount can be withdrawn in that stage is availableDepositOverflow in InteractionState object.