{"push_id":650330439,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"ec6034e2d9a355c0e46aced4728992240474c21a","before":"43aef7db3ce790e842d66e0587587de15aa0a589","commits":[{"sha":"ec6034e2d9a355c0e46aced4728992240474c21a","author":{"email":"c3d3100ac1d259bc987fcc245095221cd7e91753@conformal.com","name":"Josh Rickmar"},"message":"Modify default account naming policy.\n\nRather than disallowing the default account to be renamed as was\nproposed in #245 (and implemented in #246), the default account name\nis no longer considered a reserved name by the address manager.\nInstead, it is simply the initial name used for the first initial\naccount.\n\nA database upgrade removes any additional aliases for the default\naccount in the database.  This prevents a lookup for some name which\nis not an account name from mapping to the default account\nunexpectedly (potentially preventing incorrect account usage from the\nRPC server due to bad iteraction with default parameters).\n\nAll unset account names in a JSON-RPC request are expected to be set\nnil by btcjson.  This behavior depends on btcsuite/btcd#399.\n\nAdditionally, the manager no longer considers the wildcard * to be a\nreserved account name.  Due to poor API decisions, the RPC server\noverloads the meaning of account fields to optionally allow referring\nto all accounts at a time, or a single account.  This is not a address\nmanager responsibility, though, as a future cleaner API should not use\nmultiple differet meanings for the same field across multiple\nrequests.  Therefore, don't burden down future APIs with this quirk\nand prevent incorrect wildcard usage from the RPC server.\n\nCloses #245.","distinct":true,"url":"https://api.github.com/repos/btcsuite/btcwallet/commits/ec6034e2d9a355c0e46aced4728992240474c21a"}]}