lukechampine/walrus

Issues

• Question about scalability

  #15 opened 2 years ago by jkawamoto
  8

• Get limbo API doesn't return transaction IDs and limboSince

  #18 opened 4 years ago by jkawamoto
  3

• Couldn't initialize walrus server: cannot upgrade database for Foundation hardfork after activation height

  #17 opened 4 years ago by jkawamoto
  8

• Balance looks like it's not correct

  #14 opened 4 years ago by jkawamoto
  4

• renter.HostKeyResolver

  #13 opened 4 years ago by jkawamoto
  1

• go get fails with sk.SignHash undefined error

  #12 opened 4 years ago by jkawamoto
  1

• Make transaction IDs more accessible

  #1 opened 5 years ago by lukechampine
  2

• Add "batch query" endpoints

  #10 opened 5 years ago by lukechampine
  1

• Make /filecontracts and /blockrewards consistent with other endpoints

  #11 opened 5 years ago by lukechampine
  0

• Can't compile because related file NebulousLabs/Sia/crypto/merkle.go give error

  #7 opened 5 years ago by vargrant
  4

• can't connect from walrus-client "http: server gave HTTP response to HTTPS client"

  #8 opened 5 years ago by vargrant
  1

• Prevent accidental seed mingling

  #2 opened 5 years ago by lukechampine
  1

• Include consensus info in most GET requests

  #5 opened 5 years ago by lukechampine
  1

• Include block height of each UTXO

  #6 opened 5 years ago by lukechampine
  1

• More transaction metadata

  #4 opened 5 years ago by lukechampine
  1

• Proposal: Remove hot wallet server

  #3 opened 5 years ago by lukechampine
  1