catalyst-network/Protocol

Issues

• Fill out Usage section in README (Protocol)

  #81 opened 4 years ago by RichardLitt
  1

• Fix for the pipeline and increase the package version

  #125 opened 5 years ago by sudhirtibrewal
  0

• Pipeline to public rust sdk to crates.io

  #101 opened 5 years ago by franssl
  0

• Add fields related to batch verification

  #94 opened 5 years ago by franssl
  0

• Add error codes

  #83 opened 5 years ago by franssl
  0

• Change EntryRangeProof to be a single field rather than multiple

  #74 opened 5 years ago by franssl
  0

• Add a Nonce to transactions to prevent double spending

  #79 opened 5 years ago by monsieurleberre
  0

• Correct spelling of mainnet

  #70 opened 5 years ago by franssl
  0

• GetMempool should return an array of transactions

  #68 opened 5 years ago by monsieurleberre
  0

• Add Default values to SigningContext

  #66 opened 5 years ago by franssl
  0

• Add signature context to protobuffs

  #62 opened 5 years ago by franssl
  0

• Use appropriate time construct in TransactionBroadcast

  #57 opened 5 years ago by monsieurleberre
  0

• rename "Delta" namespace to "Deltas"

  #51 opened 5 years ago by monsieurleberre
  0

• use timestamp in delta, rather than Int

  #53 opened 5 years ago by monsieurleberre
  0

• As an RPC server I need to be able to send back a Delta when building an GetDeltaResponse

  #49 opened 5 years ago by monsieurleberre
  1

• As a RPC client user, I need to specify the hash of the delta I am looking for when sending a GetDeltaRequest

  #48 opened 6 years ago by monsieurleberre
  0

• As a node I want a message type to broadcast new Delta Hashes

  #42 opened 6 years ago by monsieurleberre
  0

• As a developer I want a basic unit testing for the proto definitions for sanity checking

  #7 opened 6 years ago by nshCore
  2

• As a delta producer I want a message type to send my favourite candidate delta

  #37 opened 6 years ago by monsieurleberre
  0

• as a network user I want to be able to broadcast candidate deltas

  #32 opened 6 years ago by monsieurleberre
  0

• As a protocol user I need a CorrelationId field on all reponse messages

  #18 opened 6 years ago by monsieurleberre
  0

• As a developer I want to know the transaction field structure documentation.

  #3 opened 6 years ago by nshCore
  0

• As a developer I want to have PeerId definition at the protocol level

  #12 opened 6 years ago by monsieurleberre
  0

• As a developer I want to have a wrapper type for all message sent over P2P and RPC

  #13 opened 6 years ago by monsieurleberre
  0

• As a developer I want to get CS files generated from Proto from the build

  #11 opened 6 years ago by monsieurleberre
  1

• As protocol user I want an enum with all types of messages available

  #5 opened 6 years ago by monsieurleberre
  1