Phase 4 : Transmission Protocols #153
Victor-Salomon
started this conversation in
Ideas
Replies: 1 comment 3 replies
-
Here is my humanized type TransmissionEntity @entity {
id: ID!
nftId: String! @index
from: String!
to: String!
isActive: Boolean!
kind: String! #protocol kind
endBlock: Int
consentList: [String]
currentConsent: [String]
threshold: Int
cancellationType: String #cancellation type
cancellationBlock: Int
createdAt: Date!
updatedAt: Date!
timestampCreate: Date!
timestampUpdated: Date!
timestampTransmitted: Date!
} However I don't think is a good idea to mix 'kind' and 'type', what do you think @Victor-Salomon ? |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
TRANSMISSION
WIP - This document specifies the design choices took for the Transmission Protocols pallet implementation in the SDK.
Feel free to comment on certain misunderstandings and new suggestions are warm welcomed.
Sections:
Events
In order to make the returned events datas usefull, we provide both the native format and a friendly ready to use format design format :
6 new events are triggered by the chain in the module transmissionProtocols.
SDK events
Additional events will be added to the EventType enum in src > events.ts in the SDK:
Extrinsics
4 extrinsics will be implemented for the transmissionProtocols pallet.
Each helperTx will be duplicated by another helper version with 2 additional parameters: the keyring that will be used to sign and submit the transaction, and a waitUntil callback parameter, to define at which point we want to get the results of the transaction execution.
Storage
7 storage getters will be implemented for the transmissionProtocols pallet.
Constants
4 getters will be implemented for the transmissionProtocols pallet.
Beta Was this translation helpful? Give feedback.
All reactions