Skip to content
Permalink
Branch: master
Commits on Mar 23, 2014
  1. bugfix: correct expiration of multiple accept offers that expire on a…

    grazcoin committed Mar 23, 2014
    … single block
    
    The mechanism that checks expiration of accept offers uses a dictionary
    for alarms which contains expration block number as a key and a list of accept txid
    that expire at that block.
    While iterating on the list, the code removed checked accept txid from that list
    In a case where multiple accept transactions expire in a single block, this removal
    causes the second accept expiration to be skipped.
    specifically, this unpaid accept offer was hanging in a non expired state:
    https://masterchain.info/sellaccept.html?tx=5737353a669583964a296ef920837fd97ad5c89c3dee9e8216e674dad5c76c6e&currency=MSC
    avoiding the removal of old alerts from this dictionary fixes the problem
    
    This is the only case that such a problem has happened.
    The effect was a wrong calculation of the following accept offer (missing 1.3 MSC):
    https://masterchain.info/sellaccept.html?tx=d846fd98dcd268f835d272e13b8623fd2ca435060fa91baaf8426bffb067a5b1&currency=MSC
    but since we could see that the later payment was correct, and the consensus support it,
    I see no problem to correct this problem retrospective.
    
    If the foundation insists, I could still keep the bug until current block.
Commits on Mar 21, 2014
  1. avoid google translation and caching of html pages

    grazcoin committed Mar 21, 2014
    sync also html_includes to auto generate the updated html
Commits on Mar 20, 2014
  1. invalidate tx with multiple outputs to exodus

    grazcoin committed Mar 20, 2014
    if a transaction does not originate from exodus, do not
    allow multiple outputs to exodus
    
    example:
    https://masterchain.info/simplesend.html?tx=f1a0f43f10c3af7eff7b998ef0eb82f0eb82698f3752b27486e5537895207d51
    has 2 outputs of 5460 satoshi to exodus
Commits on Mar 17, 2014
Commits on Mar 16, 2014
  1. allow case of different reserved funds and accepted on sell offer update

    grazcoin committed Mar 16, 2014
    Such a case may be caused by a bug, but in some cases it is a normal behavior
    the trigger for this change is:
    https://masterchain.info/selloffer.html?tx=b4fff0b33a547078cbde9a824a71a1d1ecdc6d234c0a2ac5df9123e129fa44a1&currency=MSC
    Although transaction got parsed well, the automatic bug alert mechanism prevented
    the sell offer from being attached to the seller address, and therefore it was
    not available on the user interface, and the reserved funds did not get update.
    Any user could have accepted this sell offer if they visited the sell offer
    page directly.
  2. invalidate tx with empty from address

    grazcoin committed Mar 16, 2014
    examle transaction:
    8fba98bc4ec872e8529433d70f1ac4f2724e0f42513214851b8155fa17522e3e
    where the input is a multisig address
Commits on Mar 14, 2014
Commits on Mar 13, 2014
  1. update title of orderbook

    grazcoin committed Mar 13, 2014
Commits on Mar 12, 2014
Commits on Mar 9, 2014
  1. add amount bought to bitcoin payment parsing

    grazcoin committed Mar 9, 2014
    show on btcpayment view
Commits on Mar 6, 2014
Commits on Mar 4, 2014
  1. fix reversed sell offer order on bitcoin payment

    grazcoin committed Mar 4, 2014
    it caused under certain conditions to a mismatch of accept and sell orders
Commits on Mar 3, 2014
  1. update reserved funds of old sell offer when accept expires

    grazcoin committed Mar 3, 2014
    if sell offer got updated during a running accept against an old sell offer,
    drop the reserved funds due to that accept when it expires
    
    discussed on:
    https://bitcointalk.org/index.php?topic=292628.msg5487346#msg5487346
Commits on Mar 2, 2014
Commits on Mar 1, 2014
  1. update README

    grazcoin committed Mar 1, 2014
Commits on Feb 28, 2014
  1. set order book title

    grazcoin committed Feb 28, 2014
Commits on Feb 26, 2014
Older
You can’t perform that action at this time.