1. 07 May, 2016 1 commit
  2. 04 May, 2016 1 commit
  3. 21 Apr, 2016 1 commit
  4. 13 Apr, 2016 1 commit
  5. 23 Feb, 2016 1 commit
  6. 01 Feb, 2016 4 commits
    • David Vorick's avatar
      fix spelling errors · 10cbe2d6
      David Vorick authored
    • David Vorick's avatar
      add human readable conversions to storage prices · f2e3c1f9
      David Vorick authored
      Storage prices as interprested by the consensus package are in the units
      'Hastings per Block per Byte'. Now there are functions in the modules
      package to correctly convert between that and SC / TB / Mo.
      That conversion is currently defined in multiple places throughout the
      repo and has caused errors in the past. Now the conversion is defined in
      a single place and has a significant amount of testing to ensure that
      the conversion is happening correctly.
      TB was chosen as the base unit for space because when dealing with large
      volumes of storage TB is a lot easier to read. Furthermore, it's not
      super unreasonable that a host would want to go below 1 SC / GB / Mo,
      but lower than 1 SC / TB / Mo is effectively zero for any human level
      comprehension, even when storing data for many months.
      The value in the api test changed because there is now improved
      precision in the conversion as compared to the original conversion.
    • David Vorick's avatar
      add linting for the modules package · 9ead966c
      David Vorick authored
      The makefile code needed to be changed as well to support multi-package
    • David Vorick's avatar
      replace host.maxContractLen with modules.MaxfileContractSetLen · d0d84850
      David Vorick authored
      host.maxContractLen was a misleading constant, it was not the file
      contract that was being checked for a size but the transaction set that
      contains all of the unconfirmed dependencies of the file contract.
      Because the constant was relevant to both the renter and the host, it
      made sense to move the constant to the modules package.
      The constant is currently based off of the TransactionSetSizeLimit. As
      scalability improves on the network, it might make sense to reduce this
      number substantially. While there is a weak connection between the two,
      there is no inherent reason that the host should be limiting incoming
      transactions based on the TransactionSetSizeLimit (other than having it
      as an upper bound), and therefore a separate constant is used. An extra
      buffer of 1kb is allowed because the transaction set is going to be
      expanded during negotiation when details are added and the signatures
      are added.
      A sanity check has also been added, because it will never make sense for
      the MaxFileContractSetLen to be larger than the transaction pool limit.