New Monero”Beryllium Bullet” update provides major improvements, bug fixes

Riccardo “fluffypony” Spagni of Monero announced today the v0.13.0 release of the Monero software. This is a major release due to the October 18th network update.

This in turn enabled Bulletproofs for reduced transaction sizes, sets the ringsize globally to 11 for uniformity of transactions, updated the PoW algorithm to CNv2, and finally sets the max transaction size at half of the penalty-free block size.

Spagni says this 0.13.0 “Beryllium Bullet” release performs a number of major improvements to Monero, including a deep range of bug fixes.

Highlights of this major release are:

  • New Docker file for 64 bit Android
  • Ledger code overhaul using HIDAPI
  • Blackballing tool allows the wallet to avoid selecting known spent outputs in its rings
  • Depends system to be used as a base for reproducible builds
  • Generic M/N multisig with M < N-1
  • Translation updates
  • Non ASCII seed input for Windows
  • The spend key is now optionally held encrypted in memory
  • More memory wiping to avoid secret data lingering in memory
  • Block and transaction notifcation system
  • New set of DNSSEC supporting default DNS servers
  • Support for DNSSEC keys rollover
  • Many minor fixes from Coverity reports
  • Memory containing secret data is now locked so it won’t get swapped (Linux)
  • Preliminary support for non-Ledger hardware wallets
  • Fix for blockchain format conversion crash corner case
  • Warn about old style unencrypted payment IDs usage
  • Building now places objects/binaries in a separate directory for each branch
  • Multi output bulletproofs
  • Many bulletproof speedups
  • Fake output selection improvements (mostly using a gamma distribution)
  • monero-wallet-rpc now has a daemon mode
  • Cryptonight variant 2
  • Travis build bot
  • Fixes for --generate-from-json using the wrong wallet filename
  • Build fixes for s390x, ARM, Android, Windows, Docker, FreeBSD
  • Easier output splitting using sweep_* commands
  • The blockchain db now stores prunable and unprunable data separately
  • Keccak fix for big endian platforms
  • New wallet creation height fix for when the daemon is not running
  • New Keccak incremental update mode
  • Removal of obsolete transfer_original code
  • Transaction fees are now per byte, rather than per kilobyte
  • Transaction fees and block size/weight limit now consider notional size (“weight”) to account for non-size-linear verification time
  • New update_available flag in get_info RPC
  • Some minor ringct verification speedup
  • Include cumulative difficulty in RPC block header data
  • Blocks now have a max weight for a single transaction
  • New expect and related objects
  • NetBSD support
  • Many more performance tests
  • Remove tiny bias in random EC scalar generation
  • Ring size is now fixed to 11 in the general case
  • Performance tests can now report min, median and standard deviation
  • Aligned memory allocator
  • Terse mode for performance tests
  • unbound and miniupnpc are now git submodules
  • start_mining RPC now reports whether the daemon is already mining instead of a generic error
  • Use more exploit mitigation build options where possible
  • cmake >= 3.5 is now needed
  • Network connections now bind to the correct IP
  • Error out when --wallet-file and --wallet-dir are both used at the same time
  • Daemon start time is now withheld when running with --restricted-rpc
  • New close_wallet RPC
  • Fix for the wallet giving up scanning a transaction at the first invalid public key
  • RPC password can now be set using the RPC_LOGIN environment variable
  • simplewallet can now use a monero: URI directly
  • cn_deserialize can now extract payment IDs from transactions
  • The daemon now warns about performance if it detects the blockchain is on a rotating hard disk
  • Fix seed usage on big endian platforms
  • Compare secret keys in constant time
  • New refresh wallet RPC
  • Fix wallet going out of sync when it fails to parse a transaction
  • Fix wallet failing to load after its internal cached hash chain goes out of sync
  • Translation files are now handled when cross compiling
  • Fix txpool code infinite loop if a database error occurs
  • Speed up get_output_distribution a lot by caching data in the blockchain database
  • Some HTTP parsing speedups
  • New change_wallet_password RPC
  • Block template caching for performance
  • simplewallet now understands named priority levels, in additions to numbers
  • Resize the blockchain more conservatively
  • Fix earliest fork height caching in wallet
  • Core dumps are now disabled in wallet release binaries since they would contain secret data
  • The logger will now print to the console if the logger isn’t live
  • Sync blockchin based on bytes received, not blocks received, for better performance
  • New codefresh pipeline
  • New blockchain_depth and blockchain_ancestry statistics tools
  • The wallet can now use a user defined number of Cryptonight rounds for its KDF
  • simplewallet now warns about unrecoverable data when rescan_blockchain is run
  • Fix for race in network connection shutdown
  • Fix for simplewallet misreporting long times
  • Fix sanity checking of update record hashes
  • simplewallet now points out coinbase outputs in show_transfer
  • 0MQ correctness and performance improvements
  • Fix for simplewallet dividing by 0 on an invalid dameon response
  • New get_address_index wallet RPC
  • getbalance RPC now accepts a set of address indices
  • New set_tx_key simplewallet command to import tx keys from other wallets
  • --log-file now handles filenames without directories
  • RPC JSON error response now include the JSON version
  • Syncing messages now include a percentage done and blocks left to sync
  • Fix quadratic complexity in import_key_images
  • New locked_sweep_all simplewallet command
  • Make tests use temporary files in a writable directory
  • Fix wallet language detection when using --use-english-language-names
  • Integrated addresses can now be made for an arbitrary address
  • Do not sync read only databases
  • Build fix for boost 1.67
  • core tests now have a --filter option
  • miniupnpc, rapidjson and unbound upstream updates
  • Minor HTTP parsing fixes and speedups
  • New ignore-fractional-outputs wallet setting to ignore inputs below the fee level
  • New --regtest and --fixed-difficulty debug options
  • New generatblocks debug RPC
  • Prevent the wallet cache from being opened by more than one wallet at a time
  • UTF-8 vs UTF-16 filename conversion for windows
  • New suggested_confirmations field based on transfer amount and coinbase amount
  • Cache ringdb encryption key for speed
  • Threading improvements
  • Wallet refresh speedups
  • alt_chain_info can now show a particular chain
  • Fix read buffer overflow in import_key_images
  • New get_transaction_pool_hashes JSON RPC
  • Lower subaddress lookahead when using a hardware wallet
  • Report the blockchain size in getinfo
  • Report block hash and height when finding a block
  • Fix double header in unsigned transaction file when cold signing
  • Fix thoretical P2P layer wedge when getting incoming connection cancellations at just the right time
  • Fix lengthy delay when setting auto-refresh off at the wrong time
  • Fix 0MQ bind call when address and/or port are empty
  • Add disclaimer in the README that third party data is, well, third party, and thus differently trusted
  • Fix wallet RPC crashes when there is no open wallet
  • Fix wallet crash when using a newly created account
  • Batch transactions are now enabled by default in LMDB
  • Quantize starting refresh height when starting up the wallet, to help against fingerprinting
  • New --max-log-files command line option
  • simplewallet can now set to ignore unmixable outputs (run rescan_spent to undo)
  • Fix incorrect fee for split transactions
  • Report db version number when it is incompatible
  • P2P command line options now accept hostnames as well as IP addresses
  • Adaptive connection timeout system, to mitigate against DoS
  • simplewallet does not prompt for a missing payument ID when sending to subaddresses only
  • Log rotation now numbers files if getting current time fails
  • simplewallet can now take a filename with rings in th set_ring command
  • Fix cold signing with bulletproofs
  • --guard-against-pwnage is now --dangerous-unverified-import in blockchain-import, and it now warns and pauses
  • Strip copyrighted ICC profile (can’t make it up) metadata from monero icon PNG file
  • The wallet does not log by default any longer, for privacy
  • Consider Tor/I2P addresses as being non-local for daemon trust purposes
  • set_daemon wallet command now acccepts an optional trusted/untrusted argument
  • Do not try to pop blocks with unexpected version from a read only database
  • Drop P2P connection if most blocks are invalid
  • New set of wallet RPC for cold signing
  • Fix 172.16..31 local IP range detection
  • Fix readline interfering with std::cerr usage
  • New Windows debug build Makefile targets
  • Disable file size sanity check for wallet caches, which can get quite large
  • Enable/disable auto safe mode on LMDB where appropriate
  • Fix build with GCC 8.1.0
  • Warn when no incoming P2P connections are seen
  • Use correct unit for fee in simplewallet
  • Fix output shuffling for multisig
  • Fix race adding the same tx twice to the txpool
  • fix configuring version.cpp without git
  • Add warnings about inaccurate balances to to watch-only wallet
  • New unit tests
  • Many more smaller fixes, speedups, improvements and other tweaks
Contributors for this Release

This release was the direct result of 58 people who worked, largely as volunteers and altruistically. They put out 967 commits containing 37,385 new lines of code.

In no particular order they are:

  • Rafficer
  • rbrunner7
  • einsteinsfool
  • Sarang Noether
  • stoffu
  • el00ruobuob
  • HomDx
  • Jethro Grassie
  • xiphon
  • Maxim Shishmarev
  • phloatingman
  • redfish
  • SChernykh
  • m2049r
  • Judemir Ribeiro
  • Andrea
  • Lee Clagett
  • Jkat
  • Leon Klingele
  • naughtyfox
  • jcktm
  • philkode
  • MoroccanMalinois
  • itssteven
  • Dusan Klinec
  • Thaer Khawaja
  • cornfeedhobo
  • Italocoin
  • iDunk5400
  • Riccardo “fluffypony” Spagni
  • Guillaume Le Vaillant
  • Gene Peters
  • victorsintnicolaas
  • Gingeropolous
  • Tuan M. Hoang
  • luigi1111
  • hrumag
  • p8p
  • moneroexamples
  • Jonathan Cross
  • fireice-uk
  • Teutone
  • ordtrogen
  • S
  • moneromooo
  • Jean Pierre Dudey
  • whythat
  • Jorropo
  • Howard Chu
  • cryptochangements34
  • OPSXCQ
  • TheCharlatan
  • anonimal
  • artyomsol
  • Piotr Kąkol
  • Ryan Ronnander
  • k1nghat
  • Alexandro Sanchez
  • cslashm
  • Thomas Vaughan

Be the first to comment

Leave a Reply

Your email address will not be published.


*


Privacy Policy

WideBitcoin.com is committed to safeguarding your privacy. Contact us at if you have any questions or problems regarding the use of your Personal Data and we will gladly assist you.

By using this site or/and our services, you consent to the Processing of your Personal Data as described in this Privacy Policy.

Table of Contents

  1. Definitions used in this Policy
  2. Data protection principles we follow
  3. What rights do you have regarding your Personal Data
  4. What Personal Data we gather about you
  5. How we use your Personal Data
  6. Who else has access to your Personal Data
  7. How we secure your data
  8. Information about cookies
  9. Contact information

Definitions

Personal Data – any information relating to an identified or identifiable natural person.
Processing – any operation or set of operations which is performed on Personal Data or on sets of Personal Data.
Data subject – a natural person whose Personal Data is being Processed.
Child – a natural person under 16 years of age.
We/us (either capitalized or not)

Data Protection Principles

We promise to follow the following data protection principles:

  • Processing is lawful, fair, transparent. Our Processing activities have lawful grounds. We always consider your rights before Processing Personal Data. We will provide you information regarding Processing upon request.
  • Processing is limited to the purpose. Our Processing activities fit the purpose for which Personal Data was gathered.
  • Processing is done with minimal data. We only gather and Process the minimal amount of Personal Data required for any purpose.
  • Processing is limited with a time period. We will not store your personal data for longer than needed.
  • We will do our best to ensure the accuracy of data.
  • We will do our best to ensure the integrity and confidentiality of data.

Data Subject’s rights

The Data Subject has the following rights:

  1. Right to information – meaning you have to right to know whether your Personal Data is being processed; what data is gathered, from where it is obtained and why and by whom it is processed.
  2. Right to access – meaning you have the right to access the data collected from/about you. This includes your right to request and obtain a copy of your Personal Data gathered.
  3. Right to rectification – meaning you have the right to request rectification or erasure of your Personal Data that is inaccurate or incomplete.
  4. Right to erasure – meaning in certain circumstances you can request for your Personal Data to be erased from our records.
  5. Right to restrict processing – meaning where certain conditions apply, you have the right to restrict the Processing of your Personal Data.
  6. Right to object to processing – meaning in certain cases you have the right to object to Processing of your Personal Data, for example in the case of direct marketing.
  7. Right to object to automated Processing – meaning you have the right to object to automated Processing, including profiling; and not to be subject to a decision based solely on automated Processing. This right you can exercise whenever there is an outcome of the profiling that produces legal effects concerning or significantly affecting you.
  8. Right to data portability – you have the right to obtain your Personal Data in a machine-readable format or if it is feasible, as a direct transfer from one Processor to another.
  9. Right to lodge a complaint – in the event that we refuse your request under the Rights of Access, we will provide you with a reason as to why. If you are not satisfied with the way your request has been handled please contact us.
  10. Right for the help of supervisory authority – meaning you have the right for the help of a supervisory authority and the right for other legal remedies such as claiming damages.
  11. Right to withdraw consent – you have the right withdraw any given consent for Processing of your Personal Data.

Data we gather

Information you have provided us with
This might be your e-mail address, name, billing address, home address etc – mainly information that is necessary for delivering you a product/service or to enhance your customer experience with us. We save the information you provide us with in order for you to comment or perform other activities on the website. This information includes, for example, your name and e-mail address.

Information automatically collected about you
This includes information that is automatically stored by cookies and other session tools. For example, your shopping cart information, your IP address, your shopping history (if there is any) etc. This information is used to improve your customer experience. When you use our services or look at the contents of our website, your activities may be logged.

Information from our partners
We gather information from our trusted partners with confirmation that they have legal grounds to share that information with us. This is either information you have provided them directly with or that they have gathered about you on other legal grounds. See the list of our partners here.

Publicly available information
We might gather information about you that is publicly available.

How we use your Personal Data

We use your Personal Data in order to:

  • provide our service to you. This includes for example registering your account; providing you with other products and services that you have requested; providing you with promotional items at your request and communicating with you in relation to those products and services; communicating and interacting with you; and notifying you of changes to any services.
  • enhance your customer experience;
  • fulfil an obligation under law or contract;

We use your Personal Data on legitimate grounds and/or with your Consent.

On the grounds of entering into a contract or fulfilling contractual obligations, we Process your Personal Data for the following purposes:

  • to identify you;
  • to provide you a service or to send/offer you a product;
  • to communicate either for sales or invoicing;

On the ground of legitimate interest, we Process your Personal Data for the following purposes:

  • to send you personalized offers* (from us and/or our carefully selected partners);
  • to administer and analyse our client base (purchasing behaviour and history) in order to improve the quality, variety, and availability of products/ services offered/provided;
  • to conduct questionnaires concerning client satisfaction;

As long as you have not informed us otherwise, we consider offering you products/services that are similar or same to your purchasing history/browsing behaviour to be our legitimate interest.

With your consent we Process your Personal Data for the following purposes:

  • to send you newsletters and campaign offers (from us and/or our carefully selected partners);
  • for other purposes we have asked your consent for;

We Process your Personal Data in order to fulfil obligation rising from law and/or use your Personal Data for options provided by law. We reserve the right to anonymise Personal Data gathered and to use any such data. We will use data outside the scope of this Policy only when it is anonymised. We save your billing information and other information gathered about you for as long as needed for accounting purposes or other obligations deriving from law, but not longer than 1 year.

We might process your Personal Data for additional purposes that are not mentioned here, but are compatible with the original purpose for which the data was gathered. To do this, we will ensure that:

  • the link between purposes, context and nature of Personal Data is suitable for further Processing;
  • the further Processing would not harm your interests and
  • there would be appropriate safeguard for Processing.

We will inform you of any further Processing and purposes.

Who else can access your Personal Data

We do not share your Personal Data with strangers. Personal Data about you is in some cases provided to our trusted partners in order to either make providing the service to you possible or to enhance your customer experience. We share your data with:

Our processing partners:

  • facebook.com
  • google.com
  • bing.com
  • twitter.com
  • pinterest.com

Our business partners:

  • facebook.com
  • google.com
  • bing.com
  • twitter.com
  • pinterest.com

Connected third parties:

  • facebook.com
  • google.com
  • bing.com
  • twitter.com
  • pinterest.com

We only work with Processing partners who are able to ensure adequate level of protection to your Personal Data. We disclose your Personal Data to third parties or public officials when we are legally obliged to do so. We might disclose your Personal Data to third parties if you have consented to it or if there are other legal grounds for it.

How we secure your data

We do our best to keep your Personal Data safe. We use safe protocols for communication and transferring data (such as HTTPS). We use anonymising and pseudonymising where suitable. We monitor our systems for possible vulnerabilities and attacks.

Even though we try our best we can not guarantee the security of information. However, we promise to notify suitable authorities of data breaches. We will also notify you if there is a threat to your rights or interests. We will do everything we reasonably can to prevent security breaches and to assist authorities should any breaches occur.

If you have an account with us, note that you have to keep your username and password secret.

Children

We do not intend to collect or knowingly collect information from children. We do not target children with our services.

Cookies and other technologies we use

We use cookies and/or similar technologies to analyse customer behaviour, administer the website, track users’ movements, and to collect information about users. This is done in order to personalize and enhance your experience with us.

A cookie is a tiny text file stored on your computer. Cookies store information that is used to help make sites work. Only we can access the cookies created by our website. You can control your cookies at the browser level. Choosing to disable cookies may hinder your use of certain functions.

We use cookies for the following purposes:

  • Necessary cookies – these cookies are required for you to be able to use some important features on our website, such as logging in. These cookies don’t collect any personal information.
  • Functionality cookies – these cookies provide functionality that makes using our service more convenient and makes providing more personalised features possible. For example, they might remember your name and e-mail in comment forms so you don’t have to re-enter this information next time when commenting.
  • Analytics cookies – these cookies are used to track the use and performance of our website and services
  • Advertising cookies – these cookies are used to deliver advertisements that are relevant to you and to your interests. In addition, they are used to limit the number of times you see an advertisement. They are usually placed to the website by advertising networks with the website operator’s permission. These cookies remember that you have visited a website and this information is shared with other organisations such as advertisers. Often targeting or advertising cookies will be linked to site functionality provided by the other organisation.

You can remove cookies stored in your computer via your browser settings. Alternatively, you can control some 3rd party cookies by using a privacy enhancement platform such as optout.aboutads.info or youronlinechoices.com. For more information about cookies, visit allaboutcookies.org.

We use Google Analytics to measure traffic on our website. Google has their own Privacy Policy which you can review here. If you’d like to opt out of tracking by Google Analytics, visit the Google Analytics opt-out page.

Read more about cookies on our Cookie Policy

Contact Information

email: contact@widebitcoin.com

Changes to this Privacy Policy

We reserve the right to make change to this Privacy Policy.

You can configure your Internet browser, by changing its options, to stop accepting cookies completely or to prompt you before accepting a cookie from the website you visit. If you do not accept cookies, however, you may not be able to use all portions of the WideBitcoin Websites or all functionality of the Services.

Please note that disabling these technologies may interfere with the performance and features of the Services.

You may also disable cookies on the WideBitcoin Sites by modifying your settings here:

Visitor comments may be checked through an automated spam detection service.

Last Update: May 25, 2018