0.14.1 deployed to mainnet

[druspencer]

Update: 29/04/24

0.14.1 deployed to mainnet ✅

• 0.14.1 has been deployed to mainnet
• Release pr: release: 0.14.1 protocol#205

monaco-protocol/[email protected]
monaco-protocol/[email protected]

---

Highlights ✨

• Orders are now processed as order requests
  • This allows for matching at the time of order creation
  • This also moves the majority of order placement costs onto crank operators
  • The wallet placing an order now only pay rent-exemptions for their market position on that market
• A new market_liquidities account to view liquidity for a market - see account structure here

A full breakdown of the release can be found here - MonacoProtocol/protocol#190

Order Requests

If you are using the client for buildOrderInstructionUIStake or createOrderUiStake then the interface has not changed. However, for those of you building program methods directly, please note that createOrderV2 is no longer in use and has been replaced with createOrderRequest. The best illustration of the change can be seen in how buildOrderInstruction has changed within the client:

• using createOrderV2

  const instruction = await program.methods
    .createOrderV2(distinctSeed, {
      marketOutcomeIndex: marketOutcomeIndex,
      forOutcome: forOutcome,
      stake: stake,
      price: price,
    })
    .accounts({
      purchaser: provider.wallet.publicKey,
      order: orderPk,
      marketPosition: marketAccounts.data.marketPositionPda,
      systemProgram: SystemProgram.programId,
      tokenProgram: TOKEN_PROGRAM_ID,
      market: marketPk,
      marketMatchingPool: marketAccounts.data.marketOutcomePoolPda,
      marketOutcome: marketAccounts.data.marketOutcomePda,
      // eslint-disable-next-line @typescript-eslint/ban-ts-comment
      // @ts-ignore
      priceLadder: priceLadderPk == undefined ? null : priceLadderPk,
      purchaserToken: purchaserTokenAccount.data.associatedTokenAccount,
      marketEscrow: marketAccounts.data.escrowPda,
      // eslint-disable-next-line @typescript-eslint/ban-ts-comment
      // @ts-ignore
      product: productPk == undefined ? null : productPk,
    })
    .instruction();

• using createOrderRequest

  const instruction = await program.methods
    .createOrderRequest({
      marketOutcomeIndex: marketOutcomeIndex,
      forOutcome: forOutcome,
      stake: stake,
      price: price,
      distinctSeed: distinctSeed,
    })
    .accounts({
      reservedOrder: orderPk,
      payer: provider.wallet.publicKey,
      purchaser: provider.wallet.publicKey,
      marketPosition: marketAccounts.data.marketPositionPda,
      systemProgram: SystemProgram.programId,
      tokenProgram: TOKEN_PROGRAM_ID,
      market: marketPk,
      marketOutcome: marketAccounts.data.marketOutcomePda,
      // eslint-disable-next-line @typescript-eslint/ban-ts-comment
      // @ts-ignore
      priceLadder: priceLadderPk == undefined ? null : priceLadderPk,
      purchaserToken: purchaserTokenAccount.data.associatedTokenAccount,
      marketEscrow: marketAccounts.data.escrowPda,
      // eslint-disable-next-line @typescript-eslint/ban-ts-comment
      // @ts-ignore
      product: productPk == undefined ? null : productPk,
      orderRequestQueue: marketAccounts.data.marketOrderRequestQueuePda,
    })
    .instruction();

Seeing Orders Onchain

• As orders are now processed via a crank method, orders will only be visible onchain once the order request has been processed
• If you are relying on checking for the orderPk account to exist to confirm your order has been created, this means you will have a longer wait for your check to confirm

Cancelling Orders

• You can only cancel your order once the order request has been processed and turned into an order

Order Request Expiry - 0.14.1

• A point release is in audit 0.14.1 to allow for an expiresOn arg to be passed on orderRequestCreation
• This allows you to control how long your orderRequest is valid for before it is dropped from the queue

---

Previous Updates

0.14.1 Audit ✅

• 0.14.1 has passed audit
• If has been deployed to bleeding-edge
  • mpDEVnZKneBb4w1vQsoTgMkNqnFe1rwW8qjmf3NsrAU
• As such, in order to minimise disruption, we will be releasing 0.14.1 on mainnet on Monday 29th April 2024
• Release pr: release: 0.14.1 protocol#205

monaco-protocol/[email protected]
monaco-protocol/[email protected]

0.14.0 Audit ✅

• 0.14.0 has passed audit
• Deploy to mainnet is scheduled for 29/04/24
  • During this time all onchain non-operator accounts will be closed

Full client releases:

@monaco-protocol/[email protected]
@monaco-protocol/[email protected]

0.14.1 Audit 🕐

• 0.14.1 is in audit
• This adds expiresOn on orderRequest (see below for more info)
• Release pr: release: 0.14.1 protocol#205

Clients:

@monaco-protocol/[email protected]
@monaco-protocol/[email protected]

Update: 03/04/2024

• 0.14.0 has been through it's first audit round and it currently in its second phase

---

Update: 12/03/2024

We have deployed 0.14.0 of the protocol to devnet-bleeding-edge for audit.

Please note that this upgrade has changed to account structures so prior to its mainnet upgrade post-audit, all non-operator accounts will be closed off meaning there will be a slight disruption on the day of the upgrade as we coordinate the closure of accounts.

Dev versions of the clients have been released:

@monaco-protocol/[email protected]
@monaco-protocol/[email protected]

As always, we don't have a timeline yet on the mainnet release but we will be sure to advise ahead of time.

Any questions, leave a message in DevHub or on Discord.

Thanks,

Dru