{"push_id":758289934,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"c8bad75a0ce56c5a4143b65b5641e0067a3ce63d","before":"4ee9eeddee31f9814843970e894586c60108f87a","commits":[{"sha":"c8bad75a0ce56c5a4143b65b5641e0067a3ce63d","author":{"email":"adc814bcde78a4ce66f68f2f46769e6abdd43145@webworks.se","name":"Jorgen Modin"},"message":"Setting network to regtest directly,\n\nin line with kirill's commits to chromanode. The reason I made regtest a\nsub setting of testnet goes back to ngccc, that some components needed\nthe \"testnet\" status to be true, for handling bitcoin addresses (since\nthose components have no knowledge of what a \"regtest\" formatted address\nwould be).\nHowever in chromanode all address conversion is handled by bitcore and\nit seems the network configuration object for regtest contains enough\ninformation for it to handle regtest addresses, so in chromanode then\nthere does not seem to be a reason to have a testnet setting being true\nwhile regtest is true.","distinct":true,"url":"https://api.github.com/repos/jeorgen/chromanode-regtest-backend/commits/c8bad75a0ce56c5a4143b65b5641e0067a3ce63d"}]}