![]() You can still control the SSE2 use manually with -4way and -4way=0. Please try this instead and let me know if it gets it right: The SSE2 auto-detect in the Linux 64-bit version doesn’t work with AMD in 64-bit mode. * Option -rpcallowip= to accept json-rpc connections from another machine. * Auto-detect whether to use 128-bit 4-way SSE2 on Linux. * Fix problem sending the last cent with sub-cent fractional change. * Only accept transactions sent by IP address if -allowreceivebyip is specified. * Internal version number from 312 to 31300. * Don’t count or spend payments until they have 1 confirmation. Note: 0.3.13 prevents problems if you haven’t already spent a 0/unconfirmed transaction, but if that already happened, you need 0.3.13.2. ![]() You should upgrade to prevent potential problems with 0/unconfirmed transactions. If you have json-rpc code that checks the contents of the error string, you need to change it to expect error objects of the form, which is the standard. Other nodes shouldn’t be able to cause an exception, and it hasn’t happened before, but if a way is found to cause an exception, this would keep it from being used to stop network nodes. * Recovers and continues if an exception is caused by a message you received. * json-rpc command line returns exit codes. * json-rpc errors return a more standard error object.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |