lukechilds
/
itchysats
mirror of https://github.com/lukechilds/itchysats.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
801 Commits
67 Branches
8 Tags
4.4 MiB
Tree: a71f619c2c
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'a71f619c2c'
${ noResults }
itchysats/daemon/sqlx-data.json

459 lines
18 KiB
Raw Normal View History

Initial daemon and frontend for taker and maker Co-authored-by: Mariusz Klochowicz <mariusz@klochowicz.com>
3 years ago
{
"db": "SQLite",
Rename `term` to `settlement_time_interval` and `announcement_lookahead` Depending on the context, this makes it more explicit what we mean by `term` in the context of the `Cfd` and the `Oracle`.
3 years ago
"07b8db7d3a709a7f06a20251d5b7251c2a3428ec73c6710a83048d6c8e974958": {
"query": "\n select\n uuid as \"uuid: crate::model::cfd::OrderId\",\n trading_pair as \"trading_pair: crate::model::TradingPair\",\n position as \"position: crate::model::Position\",\n initial_price,\n min_quantity,\n max_quantity,\n leverage as \"leverage: crate::model::Leverage\",\n liquidation_price,\n creation_timestamp_seconds as \"ts_secs: i64\",\n creation_timestamp_nanoseconds as \"ts_nanos: i32\",\n settlement_time_interval_seconds as \"settlement_time_interval_secs: i64\",\n settlement_time_interval_nanoseconds as \"settlement_time_interval_nanos: i32\",\n origin as \"origin: crate::model::cfd::Origin\",\n oracle_event_id\n\n from orders\n where uuid = $1\n ",
Revert "Db refactor"
3 years ago
"describe": {
"columns": [
{
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"name": "uuid: crate::model::cfd::OrderId",
Wire in automatic CET publication - Handles the Oracle's attestation in the cfd actor, transition according to the knowledge we have about the timelock expiry already. - Tries to publish the CET if we are in `CetStatus::Ready`, i.e. both the attestation and timelock expiry happened. We try publishing if either event happened, and just print a log in case it's not ready yet. - Tries to re-publish CET if we are in `PendingCet` upon restart. - Re-triggers CET monitoring upon startup. - Extends any state after `ContractSetup` to be able to store the attestation. (see below for ideas to change that) Things that could be done different: Currently we are carrying on the attestation through a lot of states - because we cannot just transition the user to `OpenCommitted` because it is a user decision to go for commit, but we have to keep the attestation around once it happened. To reduce the state complexity, we could store the attestation independent of the state, but associated with the cfd. This would make things a lot simpler, but we would then always have to go to the database to check if the attestation is already around (which might make other parts more complex).
3 years ago
"ordinal": 0,
Initial daemon and frontend for taker and maker Co-authored-by: Mariusz Klochowicz <mariusz@klochowicz.com>
3 years ago
"type_info": "Text"
},
{
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"name": "trading_pair: crate::model::TradingPair",
Wire in automatic CET publication - Handles the Oracle's attestation in the cfd actor, transition according to the knowledge we have about the timelock expiry already. - Tries to publish the CET if we are in `CetStatus::Ready`, i.e. both the attestation and timelock expiry happened. We try publishing if either event happened, and just print a log in case it's not ready yet. - Tries to re-publish CET if we are in `PendingCet` upon restart. - Re-triggers CET monitoring upon startup. - Extends any state after `ContractSetup` to be able to store the attestation. (see below for ideas to change that) Things that could be done different: Currently we are carrying on the attestation through a lot of states - because we cannot just transition the user to `OpenCommitted` because it is a user decision to go for commit, but we have to keep the attestation around once it happened. To reduce the state complexity, we could store the attestation independent of the state, but associated with the cfd. This would make things a lot simpler, but we would then always have to go to the database to check if the attestation is already around (which might make other parts more complex).
3 years ago
"ordinal": 1,
Initial daemon and frontend for taker and maker Co-authored-by: Mariusz Klochowicz <mariusz@klochowicz.com>
3 years ago
"type_info": "Text"
},
{
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"name": "position: crate::model::Position",
Wire in automatic CET publication - Handles the Oracle's attestation in the cfd actor, transition according to the knowledge we have about the timelock expiry already. - Tries to publish the CET if we are in `CetStatus::Ready`, i.e. both the attestation and timelock expiry happened. We try publishing if either event happened, and just print a log in case it's not ready yet. - Tries to re-publish CET if we are in `PendingCet` upon restart. - Re-triggers CET monitoring upon startup. - Extends any state after `ContractSetup` to be able to store the attestation. (see below for ideas to change that) Things that could be done different: Currently we are carrying on the attestation through a lot of states - because we cannot just transition the user to `OpenCommitted` because it is a user decision to go for commit, but we have to keep the attestation around once it happened. To reduce the state complexity, we could store the attestation independent of the state, but associated with the cfd. This would make things a lot simpler, but we would then always have to go to the database to check if the attestation is already around (which might make other parts more complex).
3 years ago
"ordinal": 2,
Refactor Cfd to be based on Order Flattening the Cfd out in the internal mode has caused duplication and confusion. This refactor puts the Order into the Cfd to make relations clearer. Note that once we have multiple leverage the leverage and liquidation price will have to move into the Cfd because they depend on the user's choice then. This should be trivial to do.
3 years ago
"type_info": "Text"
},
{
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"name": "initial_price",
Wire in automatic CET publication - Handles the Oracle's attestation in the cfd actor, transition according to the knowledge we have about the timelock expiry already. - Tries to publish the CET if we are in `CetStatus::Ready`, i.e. both the attestation and timelock expiry happened. We try publishing if either event happened, and just print a log in case it's not ready yet. - Tries to re-publish CET if we are in `PendingCet` upon restart. - Re-triggers CET monitoring upon startup. - Extends any state after `ContractSetup` to be able to store the attestation. (see below for ideas to change that) Things that could be done different: Currently we are carrying on the attestation through a lot of states - because we cannot just transition the user to `OpenCommitted` because it is a user decision to go for commit, but we have to keep the attestation around once it happened. To reduce the state complexity, we could store the attestation independent of the state, but associated with the cfd. This would make things a lot simpler, but we would then always have to go to the database to check if the attestation is already around (which might make other parts more complex).
3 years ago
"ordinal": 3,
Refactor Cfd to be based on Order Flattening the Cfd out in the internal mode has caused duplication and confusion. This refactor puts the Order into the Cfd to make relations clearer. Note that once we have multiple leverage the leverage and liquidation price will have to move into the Cfd because they depend on the user's choice then. This should be trivial to do.
3 years ago
"type_info": "Text"
},
{
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"name": "min_quantity",
Wire in automatic CET publication - Handles the Oracle's attestation in the cfd actor, transition according to the knowledge we have about the timelock expiry already. - Tries to publish the CET if we are in `CetStatus::Ready`, i.e. both the attestation and timelock expiry happened. We try publishing if either event happened, and just print a log in case it's not ready yet. - Tries to re-publish CET if we are in `PendingCet` upon restart. - Re-triggers CET monitoring upon startup. - Extends any state after `ContractSetup` to be able to store the attestation. (see below for ideas to change that) Things that could be done different: Currently we are carrying on the attestation through a lot of states - because we cannot just transition the user to `OpenCommitted` because it is a user decision to go for commit, but we have to keep the attestation around once it happened. To reduce the state complexity, we could store the attestation independent of the state, but associated with the cfd. This would make things a lot simpler, but we would then always have to go to the database to check if the attestation is already around (which might make other parts more complex).
3 years ago
"ordinal": 4,
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"type_info": "Text"
Initial daemon and frontend for taker and maker Co-authored-by: Mariusz Klochowicz <mariusz@klochowicz.com>
3 years ago
},
{
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"name": "max_quantity",
Wire in automatic CET publication - Handles the Oracle's attestation in the cfd actor, transition according to the knowledge we have about the timelock expiry already. - Tries to publish the CET if we are in `CetStatus::Ready`, i.e. both the attestation and timelock expiry happened. We try publishing if either event happened, and just print a log in case it's not ready yet. - Tries to re-publish CET if we are in `PendingCet` upon restart. - Re-triggers CET monitoring upon startup. - Extends any state after `ContractSetup` to be able to store the attestation. (see below for ideas to change that) Things that could be done different: Currently we are carrying on the attestation through a lot of states - because we cannot just transition the user to `OpenCommitted` because it is a user decision to go for commit, but we have to keep the attestation around once it happened. To reduce the state complexity, we could store the attestation independent of the state, but associated with the cfd. This would make things a lot simpler, but we would then always have to go to the database to check if the attestation is already around (which might make other parts more complex).
3 years ago
"ordinal": 5,
Initial daemon and frontend for taker and maker Co-authored-by: Mariusz Klochowicz <mariusz@klochowicz.com>
3 years ago
"type_info": "Text"
},
{
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"name": "leverage: crate::model::Leverage",
Wire in automatic CET publication - Handles the Oracle's attestation in the cfd actor, transition according to the knowledge we have about the timelock expiry already. - Tries to publish the CET if we are in `CetStatus::Ready`, i.e. both the attestation and timelock expiry happened. We try publishing if either event happened, and just print a log in case it's not ready yet. - Tries to re-publish CET if we are in `PendingCet` upon restart. - Re-triggers CET monitoring upon startup. - Extends any state after `ContractSetup` to be able to store the attestation. (see below for ideas to change that) Things that could be done different: Currently we are carrying on the attestation through a lot of states - because we cannot just transition the user to `OpenCommitted` because it is a user decision to go for commit, but we have to keep the attestation around once it happened. To reduce the state complexity, we could store the attestation independent of the state, but associated with the cfd. This would make things a lot simpler, but we would then always have to go to the database to check if the attestation is already around (which might make other parts more complex).
3 years ago
"ordinal": 6,
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"type_info": "Int64"
Initial daemon and frontend for taker and maker Co-authored-by: Mariusz Klochowicz <mariusz@klochowicz.com>
3 years ago
},
{
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"name": "liquidation_price",
Wire in automatic CET publication - Handles the Oracle's attestation in the cfd actor, transition according to the knowledge we have about the timelock expiry already. - Tries to publish the CET if we are in `CetStatus::Ready`, i.e. both the attestation and timelock expiry happened. We try publishing if either event happened, and just print a log in case it's not ready yet. - Tries to re-publish CET if we are in `PendingCet` upon restart. - Re-triggers CET monitoring upon startup. - Extends any state after `ContractSetup` to be able to store the attestation. (see below for ideas to change that) Things that could be done different: Currently we are carrying on the attestation through a lot of states - because we cannot just transition the user to `OpenCommitted` because it is a user decision to go for commit, but we have to keep the attestation around once it happened. To reduce the state complexity, we could store the attestation independent of the state, but associated with the cfd. This would make things a lot simpler, but we would then always have to go to the database to check if the attestation is already around (which might make other parts more complex).
3 years ago
"ordinal": 7,
Initial daemon and frontend for taker and maker Co-authored-by: Mariusz Klochowicz <mariusz@klochowicz.com>
3 years ago
"type_info": "Text"
},
{
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"name": "ts_secs: i64",
Wire in automatic CET publication - Handles the Oracle's attestation in the cfd actor, transition according to the knowledge we have about the timelock expiry already. - Tries to publish the CET if we are in `CetStatus::Ready`, i.e. both the attestation and timelock expiry happened. We try publishing if either event happened, and just print a log in case it's not ready yet. - Tries to re-publish CET if we are in `PendingCet` upon restart. - Re-triggers CET monitoring upon startup. - Extends any state after `ContractSetup` to be able to store the attestation. (see below for ideas to change that) Things that could be done different: Currently we are carrying on the attestation through a lot of states - because we cannot just transition the user to `OpenCommitted` because it is a user decision to go for commit, but we have to keep the attestation around once it happened. To reduce the state complexity, we could store the attestation independent of the state, but associated with the cfd. This would make things a lot simpler, but we would then always have to go to the database to check if the attestation is already around (which might make other parts more complex).
3 years ago
"ordinal": 8,
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"type_info": "Int64"
Refactor Cfd to be based on Order Flattening the Cfd out in the internal mode has caused duplication and confusion. This refactor puts the Order into the Cfd to make relations clearer. Note that once we have multiple leverage the leverage and liquidation price will have to move into the Cfd because they depend on the user's choice then. This should be trivial to do.
3 years ago
},
{
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"name": "ts_nanos: i32",
Wire in automatic CET publication - Handles the Oracle's attestation in the cfd actor, transition according to the knowledge we have about the timelock expiry already. - Tries to publish the CET if we are in `CetStatus::Ready`, i.e. both the attestation and timelock expiry happened. We try publishing if either event happened, and just print a log in case it's not ready yet. - Tries to re-publish CET if we are in `PendingCet` upon restart. - Re-triggers CET monitoring upon startup. - Extends any state after `ContractSetup` to be able to store the attestation. (see below for ideas to change that) Things that could be done different: Currently we are carrying on the attestation through a lot of states - because we cannot just transition the user to `OpenCommitted` because it is a user decision to go for commit, but we have to keep the attestation around once it happened. To reduce the state complexity, we could store the attestation independent of the state, but associated with the cfd. This would make things a lot simpler, but we would then always have to go to the database to check if the attestation is already around (which might make other parts more complex).
3 years ago
"ordinal": 9,
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"type_info": "Int64"
Refactor Cfd to be based on Order Flattening the Cfd out in the internal mode has caused duplication and confusion. This refactor puts the Order into the Cfd to make relations clearer. Note that once we have multiple leverage the leverage and liquidation price will have to move into the Cfd because they depend on the user's choice then. This should be trivial to do.
3 years ago
},
{
Rename `term` to `settlement_time_interval` and `announcement_lookahead` Depending on the context, this makes it more explicit what we mean by `term` in the context of the `Cfd` and the `Oracle`.
3 years ago
"name": "settlement_time_interval_secs: i64",
Wire in automatic CET publication - Handles the Oracle's attestation in the cfd actor, transition according to the knowledge we have about the timelock expiry already. - Tries to publish the CET if we are in `CetStatus::Ready`, i.e. both the attestation and timelock expiry happened. We try publishing if either event happened, and just print a log in case it's not ready yet. - Tries to re-publish CET if we are in `PendingCet` upon restart. - Re-triggers CET monitoring upon startup. - Extends any state after `ContractSetup` to be able to store the attestation. (see below for ideas to change that) Things that could be done different: Currently we are carrying on the attestation through a lot of states - because we cannot just transition the user to `OpenCommitted` because it is a user decision to go for commit, but we have to keep the attestation around once it happened. To reduce the state complexity, we could store the attestation independent of the state, but associated with the cfd. This would make things a lot simpler, but we would then always have to go to the database to check if the attestation is already around (which might make other parts more complex).
3 years ago
"ordinal": 10,
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"type_info": "Int64"
},
{
Rename `term` to `settlement_time_interval` and `announcement_lookahead` Depending on the context, this makes it more explicit what we mean by `term` in the context of the `Cfd` and the `Oracle`.
3 years ago
"name": "settlement_time_interval_nanos: i32",
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"ordinal": 11,
"type_info": "Int64"
},
{
"name": "origin: crate::model::cfd::Origin",
"ordinal": 12,
Initial daemon and frontend for taker and maker Co-authored-by: Mariusz Klochowicz <mariusz@klochowicz.com>
3 years ago
"type_info": "Text"
},
{
Maker publishes `OracleEventId` as part of offer The latest announcement known to the maker's cfd actor is used for extracting the event id.
3 years ago
"name": "oracle_event_id",
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"ordinal": 13,
Initial daemon and frontend for taker and maker Co-authored-by: Mariusz Klochowicz <mariusz@klochowicz.com>
3 years ago
"type_info": "Text"
}
],
"parameters": {
Rename `term` to `settlement_time_interval` and `announcement_lookahead` Depending on the context, this makes it more explicit what we mean by `term` in the context of the `Cfd` and the `Oracle`.
3 years ago
"Right": 1
Initial daemon and frontend for taker and maker Co-authored-by: Mariusz Klochowicz <mariusz@klochowicz.com>
3 years ago
},
"nullable": [
false,
false,
false,
false,
false,
false,
false,
false,
Margin calculation The buy margin is calculated from `initial_price`, `quantity` and `leverage`. The sell margin is calculated from `initial_price` and `quantity` (no leverage trading for the seller at the moment). Includes several refactors: - Separate API interface for `Cfd` and `CfdOffer` when mapping `toSseEvent`. This allows internal modelling to be different than the exposed API. - Remove the profit calculation internally, it is only relevant on the UI feed API level. - Move code that is specific to taker/maker http API from `model` to the respective `routes` module. - Some simplification of the calculation model of `Usd` (could be further improved by deriving calculation traits) - Introduces `OfferOrigin` used to save the offer's origin as `mine` and `others` in the database. This is used to properly derive the CFD position from the offer.
3 years ago
false,
Refactor Cfd to be based on Order Flattening the Cfd out in the internal mode has caused duplication and confusion. This refactor puts the Order into the Cfd to make relations clearer. Note that once we have multiple leverage the leverage and liquidation price will have to move into the Cfd because they depend on the user's choice then. This should be trivial to do.
3 years ago
false,
false,
false,
false,
Initial daemon and frontend for taker and maker Co-authored-by: Mariusz Klochowicz <mariusz@klochowicz.com>
3 years ago
false
]
}
},
Rename `term` to `settlement_time_interval` and `announcement_lookahead` Depending on the context, this makes it more explicit what we mean by `term` in the context of the `Cfd` and the `Oracle`.
3 years ago
"1ea6916f2e25bdd8f4761f0810178ed3b5e52817e6440b54d2bf4e13fb786405": {
"query": "\n with ord as (\n select\n id as order_id,\n uuid,\n trading_pair,\n position,\n initial_price,\n min_quantity,\n max_quantity,\n leverage,\n liquidation_price,\n creation_timestamp_seconds as ts_secs,\n creation_timestamp_nanoseconds as ts_nanos,\n settlement_time_interval_seconds as settlement_time_interval_secs,\n settlement_time_interval_nanoseconds as settlement_time_interval_nanos,\n origin,\n oracle_event_id\n from orders\n ),\n\n cfd as (\n select\n ord.order_id,\n id as cfd_id,\n quantity_usd\n from cfds\n inner join ord on ord.order_id = cfds.order_id\n ),\n\n state as (\n select\n id as state_id,\n cfd.order_id,\n cfd.quantity_usd,\n state\n from cfd_states\n inner join cfd on cfd.cfd_id = cfd_states.cfd_id\n where id in (\n select\n max(id) as id\n from cfd_states\n group by (cfd_id)\n )\n )\n\n select\n ord.uuid as \"uuid: crate::model::cfd::OrderId\",\n ord.trading_pair as \"trading_pair: crate::model::TradingPair\",\n ord.position as \"position: crate::model::Position\",\n ord.initial_price,\n ord.min_quantity,\n ord.max_quantity,\n ord.leverage as \"leverage: crate::model::Leverage\",\n ord.liquidation_price,\n ord.ts_secs as \"ts_secs: i64\",\n ord.ts_nanos as \"ts_nanos: i32\",\n ord.settlement_time_interval_secs as \"settlement_time_interval_secs: i64\",\n ord.settlement_time_interval_nanos as \"settlement_time_interval_nanos: i32\",\n ord.origin as \"origin: crate::model::cfd::Origin\",\n ord.oracle_event_id,\n state.quantity_usd,\n state.state\n\n from ord\n inner join state on state.order_id = ord.order_id\n\n where ord.uuid = $1\n ",
Use actual margin value for contract setup Includes validating that the amount the other party commits to is the expected amount based on calculating the counterparty margin out of the CFD values. Note: We could also remove the lock amount from the messages and use the calculation on both sides - that would simplify things.
3 years ago
"describe": {
"columns": [
{
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"name": "uuid: crate::model::cfd::OrderId",
Use actual margin value for contract setup Includes validating that the amount the other party commits to is the expected amount based on calculating the counterparty margin out of the CFD values. Note: We could also remove the lock amount from the messages and use the calculation on both sides - that would simplify things.
3 years ago
"ordinal": 0,
Wire in automatic CET publication - Handles the Oracle's attestation in the cfd actor, transition according to the knowledge we have about the timelock expiry already. - Tries to publish the CET if we are in `CetStatus::Ready`, i.e. both the attestation and timelock expiry happened. We try publishing if either event happened, and just print a log in case it's not ready yet. - Tries to re-publish CET if we are in `PendingCet` upon restart. - Re-triggers CET monitoring upon startup. - Extends any state after `ContractSetup` to be able to store the attestation. (see below for ideas to change that) Things that could be done different: Currently we are carrying on the attestation through a lot of states - because we cannot just transition the user to `OpenCommitted` because it is a user decision to go for commit, but we have to keep the attestation around once it happened. To reduce the state complexity, we could store the attestation independent of the state, but associated with the cfd. This would make things a lot simpler, but we would then always have to go to the database to check if the attestation is already around (which might make other parts more complex).
3 years ago
"type_info": "Text"
},
{
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"name": "trading_pair: crate::model::TradingPair",
Wire in automatic CET publication - Handles the Oracle's attestation in the cfd actor, transition according to the knowledge we have about the timelock expiry already. - Tries to publish the CET if we are in `CetStatus::Ready`, i.e. both the attestation and timelock expiry happened. We try publishing if either event happened, and just print a log in case it's not ready yet. - Tries to re-publish CET if we are in `PendingCet` upon restart. - Re-triggers CET monitoring upon startup. - Extends any state after `ContractSetup` to be able to store the attestation. (see below for ideas to change that) Things that could be done different: Currently we are carrying on the attestation through a lot of states - because we cannot just transition the user to `OpenCommitted` because it is a user decision to go for commit, but we have to keep the attestation around once it happened. To reduce the state complexity, we could store the attestation independent of the state, but associated with the cfd. This would make things a lot simpler, but we would then always have to go to the database to check if the attestation is already around (which might make other parts more complex).
3 years ago
"ordinal": 1,
"type_info": "Text"
},
{
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"name": "position: crate::model::Position",
Wire in automatic CET publication - Handles the Oracle's attestation in the cfd actor, transition according to the knowledge we have about the timelock expiry already. - Tries to publish the CET if we are in `CetStatus::Ready`, i.e. both the attestation and timelock expiry happened. We try publishing if either event happened, and just print a log in case it's not ready yet. - Tries to re-publish CET if we are in `PendingCet` upon restart. - Re-triggers CET monitoring upon startup. - Extends any state after `ContractSetup` to be able to store the attestation. (see below for ideas to change that) Things that could be done different: Currently we are carrying on the attestation through a lot of states - because we cannot just transition the user to `OpenCommitted` because it is a user decision to go for commit, but we have to keep the attestation around once it happened. To reduce the state complexity, we could store the attestation independent of the state, but associated with the cfd. This would make things a lot simpler, but we would then always have to go to the database to check if the attestation is already around (which might make other parts more complex).
3 years ago
"ordinal": 2,
"type_info": "Text"
},
{
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"name": "initial_price",
Wire in automatic CET publication - Handles the Oracle's attestation in the cfd actor, transition according to the knowledge we have about the timelock expiry already. - Tries to publish the CET if we are in `CetStatus::Ready`, i.e. both the attestation and timelock expiry happened. We try publishing if either event happened, and just print a log in case it's not ready yet. - Tries to re-publish CET if we are in `PendingCet` upon restart. - Re-triggers CET monitoring upon startup. - Extends any state after `ContractSetup` to be able to store the attestation. (see below for ideas to change that) Things that could be done different: Currently we are carrying on the attestation through a lot of states - because we cannot just transition the user to `OpenCommitted` because it is a user decision to go for commit, but we have to keep the attestation around once it happened. To reduce the state complexity, we could store the attestation independent of the state, but associated with the cfd. This would make things a lot simpler, but we would then always have to go to the database to check if the attestation is already around (which might make other parts more complex).
3 years ago
"ordinal": 3,
"type_info": "Text"
},
{
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"name": "min_quantity",
Wire in automatic CET publication - Handles the Oracle's attestation in the cfd actor, transition according to the knowledge we have about the timelock expiry already. - Tries to publish the CET if we are in `CetStatus::Ready`, i.e. both the attestation and timelock expiry happened. We try publishing if either event happened, and just print a log in case it's not ready yet. - Tries to re-publish CET if we are in `PendingCet` upon restart. - Re-triggers CET monitoring upon startup. - Extends any state after `ContractSetup` to be able to store the attestation. (see below for ideas to change that) Things that could be done different: Currently we are carrying on the attestation through a lot of states - because we cannot just transition the user to `OpenCommitted` because it is a user decision to go for commit, but we have to keep the attestation around once it happened. To reduce the state complexity, we could store the attestation independent of the state, but associated with the cfd. This would make things a lot simpler, but we would then always have to go to the database to check if the attestation is already around (which might make other parts more complex).
3 years ago
"ordinal": 4,
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"type_info": "Text"
Use actual margin value for contract setup Includes validating that the amount the other party commits to is the expected amount based on calculating the counterparty margin out of the CFD values. Note: We could also remove the lock amount from the messages and use the calculation on both sides - that would simplify things.
3 years ago
},
Wire in automatic CET publication - Handles the Oracle's attestation in the cfd actor, transition according to the knowledge we have about the timelock expiry already. - Tries to publish the CET if we are in `CetStatus::Ready`, i.e. both the attestation and timelock expiry happened. We try publishing if either event happened, and just print a log in case it's not ready yet. - Tries to re-publish CET if we are in `PendingCet` upon restart. - Re-triggers CET monitoring upon startup. - Extends any state after `ContractSetup` to be able to store the attestation. (see below for ideas to change that) Things that could be done different: Currently we are carrying on the attestation through a lot of states - because we cannot just transition the user to `OpenCommitted` because it is a user decision to go for commit, but we have to keep the attestation around once it happened. To reduce the state complexity, we could store the attestation independent of the state, but associated with the cfd. This would make things a lot simpler, but we would then always have to go to the database to check if the attestation is already around (which might make other parts more complex).
3 years ago
{
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"name": "max_quantity",
Wire in automatic CET publication - Handles the Oracle's attestation in the cfd actor, transition according to the knowledge we have about the timelock expiry already. - Tries to publish the CET if we are in `CetStatus::Ready`, i.e. both the attestation and timelock expiry happened. We try publishing if either event happened, and just print a log in case it's not ready yet. - Tries to re-publish CET if we are in `PendingCet` upon restart. - Re-triggers CET monitoring upon startup. - Extends any state after `ContractSetup` to be able to store the attestation. (see below for ideas to change that) Things that could be done different: Currently we are carrying on the attestation through a lot of states - because we cannot just transition the user to `OpenCommitted` because it is a user decision to go for commit, but we have to keep the attestation around once it happened. To reduce the state complexity, we could store the attestation independent of the state, but associated with the cfd. This would make things a lot simpler, but we would then always have to go to the database to check if the attestation is already around (which might make other parts more complex).
3 years ago
"ordinal": 5,
"type_info": "Text"
},
{
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"name": "leverage: crate::model::Leverage",
Wire in automatic CET publication - Handles the Oracle's attestation in the cfd actor, transition according to the knowledge we have about the timelock expiry already. - Tries to publish the CET if we are in `CetStatus::Ready`, i.e. both the attestation and timelock expiry happened. We try publishing if either event happened, and just print a log in case it's not ready yet. - Tries to re-publish CET if we are in `PendingCet` upon restart. - Re-triggers CET monitoring upon startup. - Extends any state after `ContractSetup` to be able to store the attestation. (see below for ideas to change that) Things that could be done different: Currently we are carrying on the attestation through a lot of states - because we cannot just transition the user to `OpenCommitted` because it is a user decision to go for commit, but we have to keep the attestation around once it happened. To reduce the state complexity, we could store the attestation independent of the state, but associated with the cfd. This would make things a lot simpler, but we would then always have to go to the database to check if the attestation is already around (which might make other parts more complex).
3 years ago
"ordinal": 6,
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"type_info": "Int64"
Wire in automatic CET publication - Handles the Oracle's attestation in the cfd actor, transition according to the knowledge we have about the timelock expiry already. - Tries to publish the CET if we are in `CetStatus::Ready`, i.e. both the attestation and timelock expiry happened. We try publishing if either event happened, and just print a log in case it's not ready yet. - Tries to re-publish CET if we are in `PendingCet` upon restart. - Re-triggers CET monitoring upon startup. - Extends any state after `ContractSetup` to be able to store the attestation. (see below for ideas to change that) Things that could be done different: Currently we are carrying on the attestation through a lot of states - because we cannot just transition the user to `OpenCommitted` because it is a user decision to go for commit, but we have to keep the attestation around once it happened. To reduce the state complexity, we could store the attestation independent of the state, but associated with the cfd. This would make things a lot simpler, but we would then always have to go to the database to check if the attestation is already around (which might make other parts more complex).
3 years ago
},
{
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"name": "liquidation_price",
Wire in automatic CET publication - Handles the Oracle's attestation in the cfd actor, transition according to the knowledge we have about the timelock expiry already. - Tries to publish the CET if we are in `CetStatus::Ready`, i.e. both the attestation and timelock expiry happened. We try publishing if either event happened, and just print a log in case it's not ready yet. - Tries to re-publish CET if we are in `PendingCet` upon restart. - Re-triggers CET monitoring upon startup. - Extends any state after `ContractSetup` to be able to store the attestation. (see below for ideas to change that) Things that could be done different: Currently we are carrying on the attestation through a lot of states - because we cannot just transition the user to `OpenCommitted` because it is a user decision to go for commit, but we have to keep the attestation around once it happened. To reduce the state complexity, we could store the attestation independent of the state, but associated with the cfd. This would make things a lot simpler, but we would then always have to go to the database to check if the attestation is already around (which might make other parts more complex).
3 years ago
"ordinal": 7,
"type_info": "Text"
},
{
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"name": "ts_secs: i64",
Wire in automatic CET publication - Handles the Oracle's attestation in the cfd actor, transition according to the knowledge we have about the timelock expiry already. - Tries to publish the CET if we are in `CetStatus::Ready`, i.e. both the attestation and timelock expiry happened. We try publishing if either event happened, and just print a log in case it's not ready yet. - Tries to re-publish CET if we are in `PendingCet` upon restart. - Re-triggers CET monitoring upon startup. - Extends any state after `ContractSetup` to be able to store the attestation. (see below for ideas to change that) Things that could be done different: Currently we are carrying on the attestation through a lot of states - because we cannot just transition the user to `OpenCommitted` because it is a user decision to go for commit, but we have to keep the attestation around once it happened. To reduce the state complexity, we could store the attestation independent of the state, but associated with the cfd. This would make things a lot simpler, but we would then always have to go to the database to check if the attestation is already around (which might make other parts more complex).
3 years ago
"ordinal": 8,
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"type_info": "Int64"
Wire in automatic CET publication - Handles the Oracle's attestation in the cfd actor, transition according to the knowledge we have about the timelock expiry already. - Tries to publish the CET if we are in `CetStatus::Ready`, i.e. both the attestation and timelock expiry happened. We try publishing if either event happened, and just print a log in case it's not ready yet. - Tries to re-publish CET if we are in `PendingCet` upon restart. - Re-triggers CET monitoring upon startup. - Extends any state after `ContractSetup` to be able to store the attestation. (see below for ideas to change that) Things that could be done different: Currently we are carrying on the attestation through a lot of states - because we cannot just transition the user to `OpenCommitted` because it is a user decision to go for commit, but we have to keep the attestation around once it happened. To reduce the state complexity, we could store the attestation independent of the state, but associated with the cfd. This would make things a lot simpler, but we would then always have to go to the database to check if the attestation is already around (which might make other parts more complex).
3 years ago
},
{
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"name": "ts_nanos: i32",
Wire in automatic CET publication - Handles the Oracle's attestation in the cfd actor, transition according to the knowledge we have about the timelock expiry already. - Tries to publish the CET if we are in `CetStatus::Ready`, i.e. both the attestation and timelock expiry happened. We try publishing if either event happened, and just print a log in case it's not ready yet. - Tries to re-publish CET if we are in `PendingCet` upon restart. - Re-triggers CET monitoring upon startup. - Extends any state after `ContractSetup` to be able to store the attestation. (see below for ideas to change that) Things that could be done different: Currently we are carrying on the attestation through a lot of states - because we cannot just transition the user to `OpenCommitted` because it is a user decision to go for commit, but we have to keep the attestation around once it happened. To reduce the state complexity, we could store the attestation independent of the state, but associated with the cfd. This would make things a lot simpler, but we would then always have to go to the database to check if the attestation is already around (which might make other parts more complex).
3 years ago
"ordinal": 9,
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"type_info": "Int64"
Wire in automatic CET publication - Handles the Oracle's attestation in the cfd actor, transition according to the knowledge we have about the timelock expiry already. - Tries to publish the CET if we are in `CetStatus::Ready`, i.e. both the attestation and timelock expiry happened. We try publishing if either event happened, and just print a log in case it's not ready yet. - Tries to re-publish CET if we are in `PendingCet` upon restart. - Re-triggers CET monitoring upon startup. - Extends any state after `ContractSetup` to be able to store the attestation. (see below for ideas to change that) Things that could be done different: Currently we are carrying on the attestation through a lot of states - because we cannot just transition the user to `OpenCommitted` because it is a user decision to go for commit, but we have to keep the attestation around once it happened. To reduce the state complexity, we could store the attestation independent of the state, but associated with the cfd. This would make things a lot simpler, but we would then always have to go to the database to check if the attestation is already around (which might make other parts more complex).
3 years ago
},
{
Rename `term` to `settlement_time_interval` and `announcement_lookahead` Depending on the context, this makes it more explicit what we mean by `term` in the context of the `Cfd` and the `Oracle`.
3 years ago
"name": "settlement_time_interval_secs: i64",
Wire in automatic CET publication - Handles the Oracle's attestation in the cfd actor, transition according to the knowledge we have about the timelock expiry already. - Tries to publish the CET if we are in `CetStatus::Ready`, i.e. both the attestation and timelock expiry happened. We try publishing if either event happened, and just print a log in case it's not ready yet. - Tries to re-publish CET if we are in `PendingCet` upon restart. - Re-triggers CET monitoring upon startup. - Extends any state after `ContractSetup` to be able to store the attestation. (see below for ideas to change that) Things that could be done different: Currently we are carrying on the attestation through a lot of states - because we cannot just transition the user to `OpenCommitted` because it is a user decision to go for commit, but we have to keep the attestation around once it happened. To reduce the state complexity, we could store the attestation independent of the state, but associated with the cfd. This would make things a lot simpler, but we would then always have to go to the database to check if the attestation is already around (which might make other parts more complex).
3 years ago
"ordinal": 10,
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"type_info": "Int64"
},
{
Rename `term` to `settlement_time_interval` and `announcement_lookahead` Depending on the context, this makes it more explicit what we mean by `term` in the context of the `Cfd` and the `Oracle`.
3 years ago
"name": "settlement_time_interval_nanos: i32",
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"ordinal": 11,
"type_info": "Int64"
},
{
"name": "origin: crate::model::cfd::Origin",
"ordinal": 12,
Wire in automatic CET publication - Handles the Oracle's attestation in the cfd actor, transition according to the knowledge we have about the timelock expiry already. - Tries to publish the CET if we are in `CetStatus::Ready`, i.e. both the attestation and timelock expiry happened. We try publishing if either event happened, and just print a log in case it's not ready yet. - Tries to re-publish CET if we are in `PendingCet` upon restart. - Re-triggers CET monitoring upon startup. - Extends any state after `ContractSetup` to be able to store the attestation. (see below for ideas to change that) Things that could be done different: Currently we are carrying on the attestation through a lot of states - because we cannot just transition the user to `OpenCommitted` because it is a user decision to go for commit, but we have to keep the attestation around once it happened. To reduce the state complexity, we could store the attestation independent of the state, but associated with the cfd. This would make things a lot simpler, but we would then always have to go to the database to check if the attestation is already around (which might make other parts more complex).
3 years ago
"type_info": "Text"
},
{
"name": "oracle_event_id",
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"ordinal": 13,
Wire in automatic CET publication - Handles the Oracle's attestation in the cfd actor, transition according to the knowledge we have about the timelock expiry already. - Tries to publish the CET if we are in `CetStatus::Ready`, i.e. both the attestation and timelock expiry happened. We try publishing if either event happened, and just print a log in case it's not ready yet. - Tries to re-publish CET if we are in `PendingCet` upon restart. - Re-triggers CET monitoring upon startup. - Extends any state after `ContractSetup` to be able to store the attestation. (see below for ideas to change that) Things that could be done different: Currently we are carrying on the attestation through a lot of states - because we cannot just transition the user to `OpenCommitted` because it is a user decision to go for commit, but we have to keep the attestation around once it happened. To reduce the state complexity, we could store the attestation independent of the state, but associated with the cfd. This would make things a lot simpler, but we would then always have to go to the database to check if the attestation is already around (which might make other parts more complex).
3 years ago
"type_info": "Text"
},
{
"name": "quantity_usd",
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"ordinal": 14,
Wire in automatic CET publication - Handles the Oracle's attestation in the cfd actor, transition according to the knowledge we have about the timelock expiry already. - Tries to publish the CET if we are in `CetStatus::Ready`, i.e. both the attestation and timelock expiry happened. We try publishing if either event happened, and just print a log in case it's not ready yet. - Tries to re-publish CET if we are in `PendingCet` upon restart. - Re-triggers CET monitoring upon startup. - Extends any state after `ContractSetup` to be able to store the attestation. (see below for ideas to change that) Things that could be done different: Currently we are carrying on the attestation through a lot of states - because we cannot just transition the user to `OpenCommitted` because it is a user decision to go for commit, but we have to keep the attestation around once it happened. To reduce the state complexity, we could store the attestation independent of the state, but associated with the cfd. This would make things a lot simpler, but we would then always have to go to the database to check if the attestation is already around (which might make other parts more complex).
3 years ago
"type_info": "Text"
},
{
"name": "state",
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"ordinal": 15,
Wire in automatic CET publication - Handles the Oracle's attestation in the cfd actor, transition according to the knowledge we have about the timelock expiry already. - Tries to publish the CET if we are in `CetStatus::Ready`, i.e. both the attestation and timelock expiry happened. We try publishing if either event happened, and just print a log in case it's not ready yet. - Tries to re-publish CET if we are in `PendingCet` upon restart. - Re-triggers CET monitoring upon startup. - Extends any state after `ContractSetup` to be able to store the attestation. (see below for ideas to change that) Things that could be done different: Currently we are carrying on the attestation through a lot of states - because we cannot just transition the user to `OpenCommitted` because it is a user decision to go for commit, but we have to keep the attestation around once it happened. To reduce the state complexity, we could store the attestation independent of the state, but associated with the cfd. This would make things a lot simpler, but we would then always have to go to the database to check if the attestation is already around (which might make other parts more complex).
3 years ago
"type_info": "Text"
}
],
"parameters": {
"Right": 1
},
"nullable": [
false,
false,
false,
false,
false,
false,
false,
false,
false,
false,
false,
false,
false,
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
false,
false,
Wire in automatic CET publication - Handles the Oracle's attestation in the cfd actor, transition according to the knowledge we have about the timelock expiry already. - Tries to publish the CET if we are in `CetStatus::Ready`, i.e. both the attestation and timelock expiry happened. We try publishing if either event happened, and just print a log in case it's not ready yet. - Tries to re-publish CET if we are in `PendingCet` upon restart. - Re-triggers CET monitoring upon startup. - Extends any state after `ContractSetup` to be able to store the attestation. (see below for ideas to change that) Things that could be done different: Currently we are carrying on the attestation through a lot of states - because we cannot just transition the user to `OpenCommitted` because it is a user decision to go for commit, but we have to keep the attestation around once it happened. To reduce the state complexity, we could store the attestation independent of the state, but associated with the cfd. This would make things a lot simpler, but we would then always have to go to the database to check if the attestation is already around (which might make other parts more complex).
3 years ago
false
]
}
},
Rename `term` to `settlement_time_interval` and `announcement_lookahead` Depending on the context, this makes it more explicit what we mean by `term` in the context of the `Cfd` and the `Oracle`.
3 years ago
"221a6283db798bacaba99e7e85130f9a8bbea1299d8cb99d272b1d478dc19775": {
"query": "\n select\n state\n from cfd_states\n where cfd_id = $1\n order by id desc\n limit 1;\n ",
Wire in automatic CET publication - Handles the Oracle's attestation in the cfd actor, transition according to the knowledge we have about the timelock expiry already. - Tries to publish the CET if we are in `CetStatus::Ready`, i.e. both the attestation and timelock expiry happened. We try publishing if either event happened, and just print a log in case it's not ready yet. - Tries to re-publish CET if we are in `PendingCet` upon restart. - Re-triggers CET monitoring upon startup. - Extends any state after `ContractSetup` to be able to store the attestation. (see below for ideas to change that) Things that could be done different: Currently we are carrying on the attestation through a lot of states - because we cannot just transition the user to `OpenCommitted` because it is a user decision to go for commit, but we have to keep the attestation around once it happened. To reduce the state complexity, we could store the attestation independent of the state, but associated with the cfd. This would make things a lot simpler, but we would then always have to go to the database to check if the attestation is already around (which might make other parts more complex).
3 years ago
"describe": {
"columns": [
Use actual margin value for contract setup Includes validating that the amount the other party commits to is the expected amount based on calculating the counterparty margin out of the CFD values. Note: We could also remove the lock amount from the messages and use the calculation on both sides - that would simplify things.
3 years ago
{
Rename `term` to `settlement_time_interval` and `announcement_lookahead` Depending on the context, this makes it more explicit what we mean by `term` in the context of the `Cfd` and the `Oracle`.
3 years ago
"name": "state",
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"ordinal": 0,
Rename `term` to `settlement_time_interval` and `announcement_lookahead` Depending on the context, this makes it more explicit what we mean by `term` in the context of the `Cfd` and the `Oracle`.
3 years ago
"type_info": "Text"
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
}
],
"parameters": {
"Right": 1
},
"nullable": [
Rename `term` to `settlement_time_interval` and `announcement_lookahead` Depending on the context, this makes it more explicit what we mean by `term` in the context of the `Cfd` and the `Oracle`.
3 years ago
false
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
]
}
},
Rename `term` to `settlement_time_interval` and `announcement_lookahead` Depending on the context, this makes it more explicit what we mean by `term` in the context of the `Cfd` and the `Oracle`.
3 years ago
"571575003ef3ad8ad627213f11c9080c25a29bb665077ada9047630acfe4465c": {
"query": "\n with ord as (\n select\n id as order_id,\n uuid,\n trading_pair,\n position,\n initial_price,\n min_quantity,\n max_quantity,\n leverage,\n liquidation_price,\n creation_timestamp_seconds as ts_secs,\n creation_timestamp_nanoseconds as ts_nanos,\n settlement_time_interval_seconds as settlement_time_interval_secs,\n settlement_time_interval_nanoseconds as settlement_time_interval_nanos,\n origin,\n oracle_event_id\n from orders\n ),\n\n cfd as (\n select\n ord.order_id,\n id as cfd_id,\n quantity_usd\n from cfds\n inner join ord on ord.order_id = cfds.order_id\n ),\n\n state as (\n select\n id as state_id,\n cfd.order_id,\n cfd.quantity_usd,\n state\n from cfd_states\n inner join cfd on cfd.cfd_id = cfd_states.cfd_id\n where id in (\n select\n max(id) as id\n from cfd_states\n group by (cfd_id)\n )\n )\n\n select\n ord.uuid as \"uuid: crate::model::cfd::OrderId\",\n ord.trading_pair as \"trading_pair: crate::model::TradingPair\",\n ord.position as \"position: crate::model::Position\",\n ord.initial_price,\n ord.min_quantity,\n ord.max_quantity,\n ord.leverage as \"leverage: crate::model::Leverage\",\n ord.liquidation_price,\n ord.ts_secs as \"ts_secs: i64\",\n ord.ts_nanos as \"ts_nanos: i32\",\n ord.settlement_time_interval_secs as \"settlement_time_interval_secs: i64\",\n ord.settlement_time_interval_nanos as \"settlement_time_interval_nanos: i32\",\n ord.origin as \"origin: crate::model::cfd::Origin\",\n ord.oracle_event_id,\n state.quantity_usd,\n state.state\n\n from ord\n inner join state on state.order_id = ord.order_id\n\n where ord.oracle_event_id = $1\n ",
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"describe": {
"columns": [
{
"name": "uuid: crate::model::cfd::OrderId",
Wire in automatic CET publication - Handles the Oracle's attestation in the cfd actor, transition according to the knowledge we have about the timelock expiry already. - Tries to publish the CET if we are in `CetStatus::Ready`, i.e. both the attestation and timelock expiry happened. We try publishing if either event happened, and just print a log in case it's not ready yet. - Tries to re-publish CET if we are in `PendingCet` upon restart. - Re-triggers CET monitoring upon startup. - Extends any state after `ContractSetup` to be able to store the attestation. (see below for ideas to change that) Things that could be done different: Currently we are carrying on the attestation through a lot of states - because we cannot just transition the user to `OpenCommitted` because it is a user decision to go for commit, but we have to keep the attestation around once it happened. To reduce the state complexity, we could store the attestation independent of the state, but associated with the cfd. This would make things a lot simpler, but we would then always have to go to the database to check if the attestation is already around (which might make other parts more complex).
3 years ago
"ordinal": 0,
Use actual margin value for contract setup Includes validating that the amount the other party commits to is the expected amount based on calculating the counterparty margin out of the CFD values. Note: We could also remove the lock amount from the messages and use the calculation on both sides - that would simplify things.
3 years ago
"type_info": "Text"
},
{
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"name": "trading_pair: crate::model::TradingPair",
Wire in automatic CET publication - Handles the Oracle's attestation in the cfd actor, transition according to the knowledge we have about the timelock expiry already. - Tries to publish the CET if we are in `CetStatus::Ready`, i.e. both the attestation and timelock expiry happened. We try publishing if either event happened, and just print a log in case it's not ready yet. - Tries to re-publish CET if we are in `PendingCet` upon restart. - Re-triggers CET monitoring upon startup. - Extends any state after `ContractSetup` to be able to store the attestation. (see below for ideas to change that) Things that could be done different: Currently we are carrying on the attestation through a lot of states - because we cannot just transition the user to `OpenCommitted` because it is a user decision to go for commit, but we have to keep the attestation around once it happened. To reduce the state complexity, we could store the attestation independent of the state, but associated with the cfd. This would make things a lot simpler, but we would then always have to go to the database to check if the attestation is already around (which might make other parts more complex).
3 years ago
"ordinal": 1,
Use actual margin value for contract setup Includes validating that the amount the other party commits to is the expected amount based on calculating the counterparty margin out of the CFD values. Note: We could also remove the lock amount from the messages and use the calculation on both sides - that would simplify things.
3 years ago
"type_info": "Text"
},
{
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"name": "position: crate::model::Position",
Wire in automatic CET publication - Handles the Oracle's attestation in the cfd actor, transition according to the knowledge we have about the timelock expiry already. - Tries to publish the CET if we are in `CetStatus::Ready`, i.e. both the attestation and timelock expiry happened. We try publishing if either event happened, and just print a log in case it's not ready yet. - Tries to re-publish CET if we are in `PendingCet` upon restart. - Re-triggers CET monitoring upon startup. - Extends any state after `ContractSetup` to be able to store the attestation. (see below for ideas to change that) Things that could be done different: Currently we are carrying on the attestation through a lot of states - because we cannot just transition the user to `OpenCommitted` because it is a user decision to go for commit, but we have to keep the attestation around once it happened. To reduce the state complexity, we could store the attestation independent of the state, but associated with the cfd. This would make things a lot simpler, but we would then always have to go to the database to check if the attestation is already around (which might make other parts more complex).
3 years ago
"ordinal": 2,
Use actual margin value for contract setup Includes validating that the amount the other party commits to is the expected amount based on calculating the counterparty margin out of the CFD values. Note: We could also remove the lock amount from the messages and use the calculation on both sides - that would simplify things.
3 years ago
"type_info": "Text"
},
{
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"name": "initial_price",
Wire in automatic CET publication - Handles the Oracle's attestation in the cfd actor, transition according to the knowledge we have about the timelock expiry already. - Tries to publish the CET if we are in `CetStatus::Ready`, i.e. both the attestation and timelock expiry happened. We try publishing if either event happened, and just print a log in case it's not ready yet. - Tries to re-publish CET if we are in `PendingCet` upon restart. - Re-triggers CET monitoring upon startup. - Extends any state after `ContractSetup` to be able to store the attestation. (see below for ideas to change that) Things that could be done different: Currently we are carrying on the attestation through a lot of states - because we cannot just transition the user to `OpenCommitted` because it is a user decision to go for commit, but we have to keep the attestation around once it happened. To reduce the state complexity, we could store the attestation independent of the state, but associated with the cfd. This would make things a lot simpler, but we would then always have to go to the database to check if the attestation is already around (which might make other parts more complex).
3 years ago
"ordinal": 3,
Use actual margin value for contract setup Includes validating that the amount the other party commits to is the expected amount based on calculating the counterparty margin out of the CFD values. Note: We could also remove the lock amount from the messages and use the calculation on both sides - that would simplify things.
3 years ago
"type_info": "Text"
},
{
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"name": "min_quantity",
Wire in automatic CET publication - Handles the Oracle's attestation in the cfd actor, transition according to the knowledge we have about the timelock expiry already. - Tries to publish the CET if we are in `CetStatus::Ready`, i.e. both the attestation and timelock expiry happened. We try publishing if either event happened, and just print a log in case it's not ready yet. - Tries to re-publish CET if we are in `PendingCet` upon restart. - Re-triggers CET monitoring upon startup. - Extends any state after `ContractSetup` to be able to store the attestation. (see below for ideas to change that) Things that could be done different: Currently we are carrying on the attestation through a lot of states - because we cannot just transition the user to `OpenCommitted` because it is a user decision to go for commit, but we have to keep the attestation around once it happened. To reduce the state complexity, we could store the attestation independent of the state, but associated with the cfd. This would make things a lot simpler, but we would then always have to go to the database to check if the attestation is already around (which might make other parts more complex).
3 years ago
"ordinal": 4,
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"type_info": "Text"
Use actual margin value for contract setup Includes validating that the amount the other party commits to is the expected amount based on calculating the counterparty margin out of the CFD values. Note: We could also remove the lock amount from the messages and use the calculation on both sides - that would simplify things.
3 years ago
},
{
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"name": "max_quantity",
Wire in automatic CET publication - Handles the Oracle's attestation in the cfd actor, transition according to the knowledge we have about the timelock expiry already. - Tries to publish the CET if we are in `CetStatus::Ready`, i.e. both the attestation and timelock expiry happened. We try publishing if either event happened, and just print a log in case it's not ready yet. - Tries to re-publish CET if we are in `PendingCet` upon restart. - Re-triggers CET monitoring upon startup. - Extends any state after `ContractSetup` to be able to store the attestation. (see below for ideas to change that) Things that could be done different: Currently we are carrying on the attestation through a lot of states - because we cannot just transition the user to `OpenCommitted` because it is a user decision to go for commit, but we have to keep the attestation around once it happened. To reduce the state complexity, we could store the attestation independent of the state, but associated with the cfd. This would make things a lot simpler, but we would then always have to go to the database to check if the attestation is already around (which might make other parts more complex).
3 years ago
"ordinal": 5,
Use actual margin value for contract setup Includes validating that the amount the other party commits to is the expected amount based on calculating the counterparty margin out of the CFD values. Note: We could also remove the lock amount from the messages and use the calculation on both sides - that would simplify things.
3 years ago
"type_info": "Text"
},
{
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"name": "leverage: crate::model::Leverage",
Wire in automatic CET publication - Handles the Oracle's attestation in the cfd actor, transition according to the knowledge we have about the timelock expiry already. - Tries to publish the CET if we are in `CetStatus::Ready`, i.e. both the attestation and timelock expiry happened. We try publishing if either event happened, and just print a log in case it's not ready yet. - Tries to re-publish CET if we are in `PendingCet` upon restart. - Re-triggers CET monitoring upon startup. - Extends any state after `ContractSetup` to be able to store the attestation. (see below for ideas to change that) Things that could be done different: Currently we are carrying on the attestation through a lot of states - because we cannot just transition the user to `OpenCommitted` because it is a user decision to go for commit, but we have to keep the attestation around once it happened. To reduce the state complexity, we could store the attestation independent of the state, but associated with the cfd. This would make things a lot simpler, but we would then always have to go to the database to check if the attestation is already around (which might make other parts more complex).
3 years ago
"ordinal": 6,
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"type_info": "Int64"
Use actual margin value for contract setup Includes validating that the amount the other party commits to is the expected amount based on calculating the counterparty margin out of the CFD values. Note: We could also remove the lock amount from the messages and use the calculation on both sides - that would simplify things.
3 years ago
},
{
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"name": "liquidation_price",
Wire in automatic CET publication - Handles the Oracle's attestation in the cfd actor, transition according to the knowledge we have about the timelock expiry already. - Tries to publish the CET if we are in `CetStatus::Ready`, i.e. both the attestation and timelock expiry happened. We try publishing if either event happened, and just print a log in case it's not ready yet. - Tries to re-publish CET if we are in `PendingCet` upon restart. - Re-triggers CET monitoring upon startup. - Extends any state after `ContractSetup` to be able to store the attestation. (see below for ideas to change that) Things that could be done different: Currently we are carrying on the attestation through a lot of states - because we cannot just transition the user to `OpenCommitted` because it is a user decision to go for commit, but we have to keep the attestation around once it happened. To reduce the state complexity, we could store the attestation independent of the state, but associated with the cfd. This would make things a lot simpler, but we would then always have to go to the database to check if the attestation is already around (which might make other parts more complex).
3 years ago
"ordinal": 7,
Use actual margin value for contract setup Includes validating that the amount the other party commits to is the expected amount based on calculating the counterparty margin out of the CFD values. Note: We could also remove the lock amount from the messages and use the calculation on both sides - that would simplify things.
3 years ago
"type_info": "Text"
},
{
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"name": "ts_secs: i64",
Wire in automatic CET publication - Handles the Oracle's attestation in the cfd actor, transition according to the knowledge we have about the timelock expiry already. - Tries to publish the CET if we are in `CetStatus::Ready`, i.e. both the attestation and timelock expiry happened. We try publishing if either event happened, and just print a log in case it's not ready yet. - Tries to re-publish CET if we are in `PendingCet` upon restart. - Re-triggers CET monitoring upon startup. - Extends any state after `ContractSetup` to be able to store the attestation. (see below for ideas to change that) Things that could be done different: Currently we are carrying on the attestation through a lot of states - because we cannot just transition the user to `OpenCommitted` because it is a user decision to go for commit, but we have to keep the attestation around once it happened. To reduce the state complexity, we could store the attestation independent of the state, but associated with the cfd. This would make things a lot simpler, but we would then always have to go to the database to check if the attestation is already around (which might make other parts more complex).
3 years ago
"ordinal": 8,
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"type_info": "Int64"
Use actual margin value for contract setup Includes validating that the amount the other party commits to is the expected amount based on calculating the counterparty margin out of the CFD values. Note: We could also remove the lock amount from the messages and use the calculation on both sides - that would simplify things.
3 years ago
},
{
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"name": "ts_nanos: i32",
Wire in automatic CET publication - Handles the Oracle's attestation in the cfd actor, transition according to the knowledge we have about the timelock expiry already. - Tries to publish the CET if we are in `CetStatus::Ready`, i.e. both the attestation and timelock expiry happened. We try publishing if either event happened, and just print a log in case it's not ready yet. - Tries to re-publish CET if we are in `PendingCet` upon restart. - Re-triggers CET monitoring upon startup. - Extends any state after `ContractSetup` to be able to store the attestation. (see below for ideas to change that) Things that could be done different: Currently we are carrying on the attestation through a lot of states - because we cannot just transition the user to `OpenCommitted` because it is a user decision to go for commit, but we have to keep the attestation around once it happened. To reduce the state complexity, we could store the attestation independent of the state, but associated with the cfd. This would make things a lot simpler, but we would then always have to go to the database to check if the attestation is already around (which might make other parts more complex).
3 years ago
"ordinal": 9,
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"type_info": "Int64"
Use actual margin value for contract setup Includes validating that the amount the other party commits to is the expected amount based on calculating the counterparty margin out of the CFD values. Note: We could also remove the lock amount from the messages and use the calculation on both sides - that would simplify things.
3 years ago
},
{
Rename `term` to `settlement_time_interval` and `announcement_lookahead` Depending on the context, this makes it more explicit what we mean by `term` in the context of the `Cfd` and the `Oracle`.
3 years ago
"name": "settlement_time_interval_secs: i64",
Wire in automatic CET publication - Handles the Oracle's attestation in the cfd actor, transition according to the knowledge we have about the timelock expiry already. - Tries to publish the CET if we are in `CetStatus::Ready`, i.e. both the attestation and timelock expiry happened. We try publishing if either event happened, and just print a log in case it's not ready yet. - Tries to re-publish CET if we are in `PendingCet` upon restart. - Re-triggers CET monitoring upon startup. - Extends any state after `ContractSetup` to be able to store the attestation. (see below for ideas to change that) Things that could be done different: Currently we are carrying on the attestation through a lot of states - because we cannot just transition the user to `OpenCommitted` because it is a user decision to go for commit, but we have to keep the attestation around once it happened. To reduce the state complexity, we could store the attestation independent of the state, but associated with the cfd. This would make things a lot simpler, but we would then always have to go to the database to check if the attestation is already around (which might make other parts more complex).
3 years ago
"ordinal": 10,
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"type_info": "Int64"
},
{
Rename `term` to `settlement_time_interval` and `announcement_lookahead` Depending on the context, this makes it more explicit what we mean by `term` in the context of the `Cfd` and the `Oracle`.
3 years ago
"name": "settlement_time_interval_nanos: i32",
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"ordinal": 11,
"type_info": "Int64"
},
{
"name": "origin: crate::model::cfd::Origin",
"ordinal": 12,
Revert "Db refactor"
3 years ago
"type_info": "Text"
Use actual margin value for contract setup Includes validating that the amount the other party commits to is the expected amount based on calculating the counterparty margin out of the CFD values. Note: We could also remove the lock amount from the messages and use the calculation on both sides - that would simplify things.
3 years ago
},
{
Revert "Db refactor"
3 years ago
"name": "oracle_event_id",
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"ordinal": 13,
Revert "Db refactor"
3 years ago
"type_info": "Text"
Use actual margin value for contract setup Includes validating that the amount the other party commits to is the expected amount based on calculating the counterparty margin out of the CFD values. Note: We could also remove the lock amount from the messages and use the calculation on both sides - that would simplify things.
3 years ago
},
{
Revert "Db refactor"
3 years ago
"name": "quantity_usd",
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"ordinal": 14,
Use actual margin value for contract setup Includes validating that the amount the other party commits to is the expected amount based on calculating the counterparty margin out of the CFD values. Note: We could also remove the lock amount from the messages and use the calculation on both sides - that would simplify things.
3 years ago
"type_info": "Text"
Maker publishes `OracleEventId` as part of offer The latest announcement known to the maker's cfd actor is used for extracting the event id.
3 years ago
},
{
Revert "Db refactor"
3 years ago
"name": "state",
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"ordinal": 15,
Maker publishes `OracleEventId` as part of offer The latest announcement known to the maker's cfd actor is used for extracting the event id.
3 years ago
"type_info": "Text"
Use actual margin value for contract setup Includes validating that the amount the other party commits to is the expected amount based on calculating the counterparty margin out of the CFD values. Note: We could also remove the lock amount from the messages and use the calculation on both sides - that would simplify things.
3 years ago
}
],
"parameters": {
"Right": 1
},
"nullable": [
false,
false,
false,
false,
false,
false,
false,
false,
false,
false,
false,
false,
Maker publishes `OracleEventId` as part of offer The latest announcement known to the maker's cfd actor is used for extracting the event id.
3 years ago
false,
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
false,
false,
Use actual margin value for contract setup Includes validating that the amount the other party commits to is the expected amount based on calculating the counterparty margin out of the CFD values. Note: We could also remove the lock amount from the messages and use the calculation on both sides - that would simplify things.
3 years ago
false
]
}
},
Rename `term` to `settlement_time_interval` and `announcement_lookahead` Depending on the context, this makes it more explicit what we mean by `term` in the context of the `Cfd` and the `Oracle`.
3 years ago
"8cbe349911b35d8e79763d64b4f5813b4bd98f12e0bba5ada84d2cae8b08ef4f": {
"query": "\n select\n id\n from cfds\n where order_uuid = $1;\n ",
"describe": {
"columns": [
{
"name": "id",
"ordinal": 0,
"type_info": "Int64"
}
],
"parameters": {
"Right": 1
},
"nullable": [
true
]
}
},
"b5a6bcafbfa745d147c30410e0acf8ee6c7733cc3e550a2db0c7860737c756dd": {
"query": "\n with ord as (\n select\n id as order_id,\n uuid,\n trading_pair,\n position,\n initial_price,\n min_quantity,\n max_quantity,\n leverage,\n liquidation_price,\n creation_timestamp_seconds as ts_secs,\n creation_timestamp_nanoseconds as ts_nanos,\n settlement_time_interval_seconds as settlement_time_interval_secs,\n settlement_time_interval_nanoseconds as settlement_time_interval_nanos,\n origin,\n oracle_event_id\n from orders\n ),\n\n cfd as (\n select\n ord.order_id,\n id as cfd_id,\n quantity_usd\n from cfds\n inner join ord on ord.order_id = cfds.order_id\n ),\n\n state as (\n select\n id as state_id,\n cfd.order_id,\n cfd.quantity_usd,\n state\n from cfd_states\n inner join cfd on cfd.cfd_id = cfd_states.cfd_id\n where id in (\n select\n max(id) as id\n from cfd_states\n group by (cfd_id)\n )\n )\n\n select\n ord.uuid as \"uuid: crate::model::cfd::OrderId\",\n ord.trading_pair as \"trading_pair: crate::model::TradingPair\",\n ord.position as \"position: crate::model::Position\",\n ord.initial_price,\n ord.min_quantity,\n ord.max_quantity,\n ord.leverage as \"leverage: crate::model::Leverage\",\n ord.liquidation_price,\n ord.ts_secs as \"ts_secs: i64\",\n ord.ts_nanos as \"ts_nanos: i32\",\n ord.settlement_time_interval_secs as \"settlement_time_interval_secs: i64\",\n ord.settlement_time_interval_nanos as \"settlement_time_interval_nanos: i32\",\n ord.origin as \"origin: crate::model::cfd::Origin\",\n ord.oracle_event_id,\n state.quantity_usd,\n state.state\n\n from ord\n inner join state on state.order_id = ord.order_id\n ",
Initial daemon and frontend for taker and maker Co-authored-by: Mariusz Klochowicz <mariusz@klochowicz.com>
3 years ago
"describe": {
"columns": [
{
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"name": "uuid: crate::model::cfd::OrderId",
Initial daemon and frontend for taker and maker Co-authored-by: Mariusz Klochowicz <mariusz@klochowicz.com>
3 years ago
"ordinal": 0,
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"type_info": "Text"
Initial daemon and frontend for taker and maker Co-authored-by: Mariusz Klochowicz <mariusz@klochowicz.com>
3 years ago
},
{
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"name": "trading_pair: crate::model::TradingPair",
Initial daemon and frontend for taker and maker Co-authored-by: Mariusz Klochowicz <mariusz@klochowicz.com>
3 years ago
"ordinal": 1,
"type_info": "Text"
},
{
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"name": "position: crate::model::Position",
Initial daemon and frontend for taker and maker Co-authored-by: Mariusz Klochowicz <mariusz@klochowicz.com>
3 years ago
"ordinal": 2,
"type_info": "Text"
},
{
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"name": "initial_price",
Initial daemon and frontend for taker and maker Co-authored-by: Mariusz Klochowicz <mariusz@klochowicz.com>
3 years ago
"ordinal": 3,
"type_info": "Text"
},
{
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"name": "min_quantity",
Initial daemon and frontend for taker and maker Co-authored-by: Mariusz Klochowicz <mariusz@klochowicz.com>
3 years ago
"ordinal": 4,
"type_info": "Text"
},
{
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"name": "max_quantity",
Initial daemon and frontend for taker and maker Co-authored-by: Mariusz Klochowicz <mariusz@klochowicz.com>
3 years ago
"ordinal": 5,
"type_info": "Text"
},
{
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"name": "leverage: crate::model::Leverage",
Initial daemon and frontend for taker and maker Co-authored-by: Mariusz Klochowicz <mariusz@klochowicz.com>
3 years ago
"ordinal": 6,
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"type_info": "Int64"
Initial daemon and frontend for taker and maker Co-authored-by: Mariusz Klochowicz <mariusz@klochowicz.com>
3 years ago
},
{
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"name": "liquidation_price",
Initial daemon and frontend for taker and maker Co-authored-by: Mariusz Klochowicz <mariusz@klochowicz.com>
3 years ago
"ordinal": 7,
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"type_info": "Text"
Initial daemon and frontend for taker and maker Co-authored-by: Mariusz Klochowicz <mariusz@klochowicz.com>
3 years ago
},
{
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"name": "ts_secs: i64",
Initial daemon and frontend for taker and maker Co-authored-by: Mariusz Klochowicz <mariusz@klochowicz.com>
3 years ago
"ordinal": 8,
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"type_info": "Int64"
Initial daemon and frontend for taker and maker Co-authored-by: Mariusz Klochowicz <mariusz@klochowicz.com>
3 years ago
},
{
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"name": "ts_nanos: i32",
Initial daemon and frontend for taker and maker Co-authored-by: Mariusz Klochowicz <mariusz@klochowicz.com>
3 years ago
"ordinal": 9,
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"type_info": "Int64"
Initial daemon and frontend for taker and maker Co-authored-by: Mariusz Klochowicz <mariusz@klochowicz.com>
3 years ago
},
{
Rename `term` to `settlement_time_interval` and `announcement_lookahead` Depending on the context, this makes it more explicit what we mean by `term` in the context of the `Cfd` and the `Oracle`.
3 years ago
"name": "settlement_time_interval_secs: i64",
Initial daemon and frontend for taker and maker Co-authored-by: Mariusz Klochowicz <mariusz@klochowicz.com>
3 years ago
"ordinal": 10,
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"type_info": "Int64"
Margin calculation The buy margin is calculated from `initial_price`, `quantity` and `leverage`. The sell margin is calculated from `initial_price` and `quantity` (no leverage trading for the seller at the moment). Includes several refactors: - Separate API interface for `Cfd` and `CfdOffer` when mapping `toSseEvent`. This allows internal modelling to be different than the exposed API. - Remove the profit calculation internally, it is only relevant on the UI feed API level. - Move code that is specific to taker/maker http API from `model` to the respective `routes` module. - Some simplification of the calculation model of `Usd` (could be further improved by deriving calculation traits) - Introduces `OfferOrigin` used to save the offer's origin as `mine` and `others` in the database. This is used to properly derive the CFD position from the offer.
3 years ago
},
{
Rename `term` to `settlement_time_interval` and `announcement_lookahead` Depending on the context, this makes it more explicit what we mean by `term` in the context of the `Cfd` and the `Oracle`.
3 years ago
"name": "settlement_time_interval_nanos: i32",
Margin calculation The buy margin is calculated from `initial_price`, `quantity` and `leverage`. The sell margin is calculated from `initial_price` and `quantity` (no leverage trading for the seller at the moment). Includes several refactors: - Separate API interface for `Cfd` and `CfdOffer` when mapping `toSseEvent`. This allows internal modelling to be different than the exposed API. - Remove the profit calculation internally, it is only relevant on the UI feed API level. - Move code that is specific to taker/maker http API from `model` to the respective `routes` module. - Some simplification of the calculation model of `Usd` (could be further improved by deriving calculation traits) - Introduces `OfferOrigin` used to save the offer's origin as `mine` and `others` in the database. This is used to properly derive the CFD position from the offer.
3 years ago
"ordinal": 11,
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"type_info": "Int64"
},
{
"name": "origin: crate::model::cfd::Origin",
"ordinal": 12,
Margin calculation The buy margin is calculated from `initial_price`, `quantity` and `leverage`. The sell margin is calculated from `initial_price` and `quantity` (no leverage trading for the seller at the moment). Includes several refactors: - Separate API interface for `Cfd` and `CfdOffer` when mapping `toSseEvent`. This allows internal modelling to be different than the exposed API. - Remove the profit calculation internally, it is only relevant on the UI feed API level. - Move code that is specific to taker/maker http API from `model` to the respective `routes` module. - Some simplification of the calculation model of `Usd` (could be further improved by deriving calculation traits) - Introduces `OfferOrigin` used to save the offer's origin as `mine` and `others` in the database. This is used to properly derive the CFD position from the offer.
3 years ago
"type_info": "Text"
Maker publishes `OracleEventId` as part of offer The latest announcement known to the maker's cfd actor is used for extracting the event id.
3 years ago
},
{
"name": "oracle_event_id",
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
"ordinal": 13,
Maker publishes `OracleEventId` as part of offer The latest announcement known to the maker's cfd actor is used for extracting the event id.
3 years ago
"type_info": "Text"
Rename `term` to `settlement_time_interval` and `announcement_lookahead` Depending on the context, this makes it more explicit what we mean by `term` in the context of the `Cfd` and the `Oracle`.
3 years ago
},
{
"name": "quantity_usd",
"ordinal": 14,
"type_info": "Text"
},
{
"name": "state",
"ordinal": 15,
"type_info": "Text"
Initial daemon and frontend for taker and maker Co-authored-by: Mariusz Klochowicz <mariusz@klochowicz.com>
3 years ago
}
],
"parameters": {
Rename `term` to `settlement_time_interval` and `announcement_lookahead` Depending on the context, this makes it more explicit what we mean by `term` in the context of the `Cfd` and the `Oracle`.
3 years ago
"Right": 0
Initial daemon and frontend for taker and maker Co-authored-by: Mariusz Klochowicz <mariusz@klochowicz.com>
3 years ago
},
"nullable": [
Fix up SQL queries This PR does a few things: * cleans up the SQL to make the queries clearer in terms of intent, as well as eliminating the use of an extra transaction in some write queries. * adds some additional testing * (mostly) eliminates the use of `serde_json::to_string()`, making the data columns behave in a more sane manner
3 years ago
false,
false,
Initial daemon and frontend for taker and maker Co-authored-by: Mariusz Klochowicz <mariusz@klochowicz.com>
3 years ago
false,
false,
false,
false,
false,
false,
false,
false,
false,
Margin calculation The buy margin is calculated from `initial_price`, `quantity` and `leverage`. The sell margin is calculated from `initial_price` and `quantity` (no leverage trading for the seller at the moment). Includes several refactors: - Separate API interface for `Cfd` and `CfdOffer` when mapping `toSseEvent`. This allows internal modelling to be different than the exposed API. - Remove the profit calculation internally, it is only relevant on the UI feed API level. - Move code that is specific to taker/maker http API from `model` to the respective `routes` module. - Some simplification of the calculation model of `Usd` (could be further improved by deriving calculation traits) - Introduces `OfferOrigin` used to save the offer's origin as `mine` and `others` in the database. This is used to properly derive the CFD position from the offer.
3 years ago
false,
Maker publishes `OracleEventId` as part of offer The latest announcement known to the maker's cfd actor is used for extracting the event id.
3 years ago
false,
Rename `term` to `settlement_time_interval` and `announcement_lookahead` Depending on the context, this makes it more explicit what we mean by `term` in the context of the `Cfd` and the `Oracle`.
3 years ago
false,
false,
Initial daemon and frontend for taker and maker Co-authored-by: Mariusz Klochowicz <mariusz@klochowicz.com>
3 years ago
false
]
}
}
}