dogethereum/dogethereum-contracts

Issues

• Challenger can request headers for non-existent blocks

  #50 opened 6 years ago by cat-j
  2

• hi, How is the dogethereum-bridge project going?

  #51 opened 5 years ago by terryliu98
  1

• security model for challenge game

  #47 opened 5 years ago by sidhujag
  1

• major flaw found in auxpow header parsing and auxpow POW

  #49 opened 6 years ago by sidhujag
  1

• Unlock tx are forced to have a change output

  #39 opened 6 years ago by oscarguindzberg
  1

• DogeClaimManager requires 6.5 million gas to deploy

  #42 opened 6 years ago by oscarguindzberg
  1

• Rename claimId to [superblockId or superblockHash]

  #45 opened 6 years ago by oscarguindzberg
  1

• Generate function documentation from comments using doxity

  #46 opened 6 years ago by oscarguindzberg
  0

• Optmize storage of superblocks

  #44 opened 6 years ago by oscarguindzberg
  0

• Superblock timeouts: Only count Ethereum blocks which had "space" for transactions.

  #43 opened 6 years ago by oscarguindzberg
  0

• Remove minimum cost of 1 doge token paid to operators and superblock submitters for doing a lock/unlock

  #41 opened 6 years ago by oscarguindzberg
  0

• DogeToken.doUnlock(): validate doge is a valid doge address in doUnlock()

  #40 opened 6 years ago by oscarguindzberg
  0

• Improvements to the deposit system

  #38 opened 6 years ago by oscarguindzberg
  0

• Make a plan in case of a dogecoin or ethereum chain hard forks

  #37 opened 6 years ago by oscarguindzberg
  0

• Optimise variable usage to avoid VM exceptions

  #25 opened 6 years ago by cat-j
  1

• Document how to get sample block headers from the doge blockchain for unit tests

  #31 opened 6 years ago by oscarguindzberg
  1

• bulkStoreHeaders review and optimisation

  #27 opened 6 years ago by cat-j
  0

• We might end up with orphan blocks If scrypt verification success msg is not received in the same order it was sent

  #21 opened 6 years ago by oscarguindzberg
  0

• Reduce gas usage, in particular when adding doge block headers

  #16 opened 6 years ago by oscarguindzberg
  2

• Security audit of dogerelay

  #15 opened 6 years ago by oscarguindzberg
  0

• Re evaluate how we identify block proposal to scrypt cheker

  #14 opened 6 years ago by oscarguindzberg
  0

• Add missing validations on AuxPow

  #13 opened 6 years ago by oscarguindzberg
  0

• Re-evaluate whether the validations that are done onchain (eg previous block exists) should be done before or after ScryptChecker

  #12 opened 6 years ago by oscarguindzberg
  0

• Deploy to Ropsten using Truebit's ScryptChecker instead of ScryptCheckerDummy

  #11 opened 6 years ago by oscarguindzberg
  0

• Port more unit tests from BtcRelay

  #9 opened 6 years ago by oscarguindzberg
  1

• Make DogeSubmitter open source

  #8 opened 6 years ago by oscarguindzberg
  0

• DogeRelay add incentives for pushing a block

  #7 opened 6 years ago by oscarguindzberg
  0

• Review how ScryptChecker/DogeRelay deals with invalid hashes

  #6 opened 6 years ago by oscarguindzberg
  0

• m_saveAncestors review

  #2 opened 6 years ago by oscarguindzberg
  0

• Set DogeToken address in DogeRelay during setup

  #1 opened 6 years ago by oscarguindzberg
  0

• Use continous integration

  #20 opened 7 years ago by oscarguindzberg
  1

• Fix "Comment out PoW validation until we implement doge specific code"

  #3 opened 7 years ago by oscarguindzberg
  1

• Complete block difficulty adjustement code for doge testnet

  #4 opened 7 years ago by oscarguindzberg
  1

• DogeRelay: Uncomment helperVerifyHash__ call to priv_inMainChain__

  #5 opened 7 years ago by oscarguindzberg
  2

• Make TestDogerelay.sol2 work

  #19 opened 7 years ago by oscarguindzberg
  2

• Evaluate storing doge block as struct instead of as byte array

  #24 opened 7 years ago by oscarguindzberg
  1

• Code clean up

  #28 opened 7 years ago by oscarguindzberg
  2

• Look into security measures against falsifying _truebitClaimantAddress argument in storeBlockHeader

  #30 opened 7 years ago by cat-j
  2

• Bounty Claim

  #29 opened 7 years ago by siulynot
  32

• Concerning retrieving your private key for the eth-address

  #26 opened 7 years ago by mesqueeb
  7

• Add an option for sending destination eth address in an OP_RETURN output

  #18 opened 7 years ago by oscarguindzberg
  0

• Extra validation of lock txs

  #17 opened 7 years ago by oscarguindzberg
  0

• DogeToken: review RSK's bridge contract and copy checks done before accepting a tx.

  #10 opened 7 years ago by oscarguindzberg
  1