Skip to main content

v1 Transaction breaking change

We're making a small breaking change to our Transaction resource.

The name is no longer parented with a Transfer name, and instead we're adding a new origin field.

This change is being made to supporting Staking operations, which will result in creating transactions, similar to Transfer. Given the change being small, and the early adoption of new Transaction resource, we'd like to make an unstable change without forcing an API version increment.

Endpoints GET /v1/transactions and GET /v1/transfers/:tranfer/transactions will continue to work the same.

Before​

{
  "name": "transfers/1/transactions/2",
  "state": "preparing"
  // ...
}

After​

{
  "name": "transactions/2",
  "origin": "transfers/1",
  "state": "preparing"
  // ...
}

Or

{
  "name": "transactions/3",
  "origin": "staking/1",
  "state": "preparing"
  // ...
}

Affected Treasury versions​

Treasury <=24.1.x has the old behaviour.

Treasury >=24.2.0 will have the new behaviour.