#1352 BUGFIX: Update config for new nodes to use correct BB endpoints. #1350 Add a migration to fix Blockbook endpoints. #1349 Update multiwallet with zcash patches
#1343 Update multiwallet dependency for blockbook cashaddr conversion #1328 Fix bug in multiwallet calculating value #1259 Currencies in profile no longer duplicate on update #1264 Add nil check to addresses in transaction listener #1225#1177#1207 Testing pb.Countr圜odes, allow_alias SWAZILAND, ESWATINI #1265 Isolate dependencies in repo/db/utxos_test.go #1258 Remove unused Python modules in qa/chat.py #1229 Test for MessageProcessingOrder omissions #1385 Update multiwallet with locking refactor #1347 Migrate multiwallet config Refactor multiwallet config handling #1298 Remove DuoSearch dead bootstrap node
#1242 Isolate dependencies in repo/db/stxo_test.go #1401 Add websocket read/write error logging #1382 Update message sender to respect context timeout when sending messages #1358 Update multiwallet dep with socket logging #1335 Restore order association on legacy spend #1338 Merge multiwallet dependency changes #1329 Use in-house blockbook endpoints as defaults #1277 Retry failed STORE against push nodes #1293 v: Use bitcoind 0.16.3 Install requirements.txt #1263 Removed temporary check of bitcoin cash address #1273 Use orderID in transaction listener
#1223 Add price and listingType fields to order websocket notification The old and new defaults are described in this article. In order to continue using your previous datastore, you can safely remove the newly created version and pass in the old path explicitly using the -d flag or manually move it to the new location. If the daemon is used without passing the -d flag to specify the location of the data, the daemon will create a new datastore (which looks like): Generating Ed25519 keypair.Done in the output. Important Note: Default data location in this release has changed. You can still use an SPV wallet for BTC and BCH but you'll need to configure it manually in the config file.Īs always please report any issues that you may uncover in the course of using OpenBazaar to us here on Github. Hence the default configuration is slightly lighter than past versions of OpenBazaar because it's no longer using the SPV wallets by default. It connections to a BlockBook backend server for the purpose of getting blockchain data. To support this feature we've written a multiwallet library which handles the sending/receiving and various other wallet functions for each coin. The coins supported with this release are Bitcoin, Bitcoin Cash, Litecoin, and ZCash (t-address only). This release introduces the ability to accept multiple coins for payment at the same time. Prior to this release you could accept other currencies than Bitcoin but you could only use one coin at a time. This is a major release which introduces the new multiwallet functionality into OpenBazaar.
0 kommentar(er)
