Press J to jump to the feed. Press question mark to learn the rest of the keyboard shortcuts
134

PSA: Users, (solo)miners, exchanges/merchants, and pool operators must be on v0.10.1 in advance of the hardfork otherwise you will get forked/booted off the network. Miners, please contact your pool operator to ask them if they have upgraded | Monero v0.10.1 released - mandatory upgrade!

134
Posted by
Moderator
3 years ago
Archived

PSA: Users, (solo)miners, exchanges/merchants, and pool operators must be on v0.10.1 in advance of the hardfork otherwise you will get forked/booted off the network. Miners, please contact your pool operator to ask them if they have upgraded | Monero v0.10.1 released - mandatory upgrade!

Approximately the 9th of January there will be a hardfork on the Monero network. Most pools have upgraded or are in the process of upgrading, but some have not upgraded yet. If they don't upgrade before the hardfork they will get forked/booted off the network. As a result you will miss out on revenue if you are mining on these pools. Thus, if you are mining on one of the pools that hasn't upgraded yet or hasn't scheduled an upgrade, please contact your pool owner as soon as possible and urge them to upgrade. Alternatively, you can switch to a pool that is on the right version.

PoolUpgradedContact
MoneroHashYESadmin@monerohash.com & https://monerohash.com/#support
MoneroWorldYESgingeropolous@tutanota.com & https://moneroworld.com/#support
mineXMRYESinfo@minexmr.com & http://minexmr.com/#support
PoolToYESadmin@poolto.be & http://webchat.freenode.net/?channels=%23poolto.be
MoneropoolYESsupport@moneropool.com & https://moneropool.com/#support
ProhashYESnetprohash@gmail.com & http://xmr.prohash.net/#support
Crypto-poolYESmine@crypto-pool.fr & http://monero.crypto-pool.fr/
DwarfpoolYESadmin@dwarfpool.com & http://dwarfpool.com/contact/
AlimabiYES860838000@qq.com & http://xmr.alimabi.cn/#support
CryptMoneroYESsupport@cryptmonero.com & http://cryptmonero.com/#support
MinergateYEShttps://forum.minergate.com/
SupportXMRYESsupport@supportxmr.com & http://supportxmr.com/#support
XMRpoolYESxmrpool.eu@protonmail.com & http://xmrpool.eu/#support
SheepmanYESsheepmanbb@gmail.com & http://sheepman.mine.bz/#support
CoolPoolYEScoolpool@protonmail.ch & http://xmr.coolpool.io/#support
US.toYEShttp://monero.us.to/#support
MakeXMRYESsupport@makexmr.com & https://makexmr.com/#support
USXmrPoolYESsupport@usxmrpool.com & https://www.usxmrpool.com/#support
SuprNovaYEShttps://xmr.suprnova.cc/index.php?page=contactform&action=
PoolDDYESxmr@pooldd.com & http://pooldd.com/#support
XMRpool.netYES-
XMRpool MurmansoftYESsupport@cryppit.com & rasim-82@mail.ru & http://xmrpool.murmansoft.ru/#support
XMR MiningspeedYESinfo@miningspeed.com & http://xmr.miningspeed.com/#support
  • IN PROCESS means the pool operator stated that he is in the process of upgrading.

  • UNCONFIRMED means that we haven't heard from the pool operator yet. This doesn't imply he isn't in the process or has already upgraded though.

  • If your pool has upgraded, please contact me and I'll change the status.

  • If your pool isn't listed here, please contact me and I'll add you.

An important message for pool operators and miners

From MoneroMooo:

To all pool operators:

If you haven't already, you will need to update the node-cryptonote-util software in order for your pool to cross the january fork. I think many of the pool ops have done so already, but for those who are not in #monero-pools, you will need this patch: https://paste.fedoraproject.org/506116/17116821/

This applies to zone117x's version of the pool. There is a version of this ported to clintar's fork, which is here: https://github.com/M5M400/node-cryptonote-util/commit/37f50f9b535f0258c3a1c6f7247a891b4c211ff3.

If you're not running this when the fork happens, you will be forked off.

For pool miners, you may want to check with your pool op that they're running the patch a few days before the fork, and switch to a known good pool otherwise. Please prefer smaller pools when doing so.

Also bear in mind that running v0.10.1 or the GUI beta is mandatory. Any other versions will get booted off the network. Thus, miners, please email your pools and ask them if they are running v0.10.1 and have applied aforementioned patch.

General hardfork information

The upcoming fork will enable Ring Confidential Transactions. This will significantly enhance Monero's privacy. Note that they will not be enforced yet. That is, this hardfork will enable them, whereas the hardfork of September 2017 will enforce them. If you want to read more about Ring Confidential Transactions, see:

https://lab.getmonero.org/pubs/MRL-0005.pdf

https://monero.stackexchange.com/questions/tagged/ringct

Due to variance the hard fork will likely be on the 9th or 10th of January. A specific block height was determined for the hardfork, not a specific date. The specific blockheight for the hardfork can be found here. That is:

// version 4 starts from block 1220516

As an user you need to run either v0.10.1 or the Monero Core GUI Beta 1.


Monero v0.10.1 - Wolfram Warptangent - release

First and foremost, please upgrade to this version. A blockchain resync is not needed. Only this version will work after the fork of January 5. Note that this fork will enable Ring CT transactions, but will not enforce them yet.

Overview

This is a necessary point release of Monero v0.10 "Wolfram Warptangent", and is highly recommended as it includes consensus-changing fixes to the RingCT implementation and various other bug fixes.

Some highlights of this release are:

  • major changes to support the GUI

  • adds full support for "fluffy blocks", a propagation improvement similar to Compact Blocks in Bitcoin Core

  • adds in a dynamic fee system

  • expansion of the data stored in the wallet cache, including the GUI address book

  • switch to Borromean signatures in RingCT

  • add Monero payment URI support to the wallet library

  • complete overhaul of the threading system

  • optimise the wallet blockchain refresh mechanism

  • created a contributing guide

  • switched to a dynamic dust threshold system

  • added a command to compute the total coinbase

  • major RingCT performance improvements

  • killed off the old fast_exit mechanism, which caused more issues than anything else

  • improved and fixed the cold wallet transaction signing mechanism

  • overhauled the sweep_unmixable implementation

  • fixed FreeBSD builds

Official Download Links:

All available binaries can be found on the getmonero download page or on Github (at the bottom).

Official Direct Links:

Download Hashes

If you would like to verify that you have downloaded the correct file, please use the following SHA256 hashes:

  • monero.win.x64.v0-10-1-0.zip, 727a53dd154b61fd653f81da27788077fdf519301c81d3c1eb033c1ff2bf97c6

  • monero.win.x86.v0-10-1-0.zip, ce77137b33bcaeb59273cb73b86e426e35e6209fb52a7e74fd9432a5a3018041

  • monero.mac.x64.v0-10-1-0.tar.bz2, 447cebae257864b3706a8622f495bfd9fae780a6b277e1e31ac83bef7bc855c6

  • monero.linux.x64.v0-10-1-0.tar.bz2, bf09eea27c957e7e2bdd62dac250888b301d4d25abe18d4a5b930fa7477708c7

  • monero.linux.x86.v0-10-1-0.tar.bz2, 9a18d274970df85d6bc926dc99407959c680c36f19017996be9c758f6c02cf06

  • monero.linux.arm7.v0-10-1-0.tar.bz2, 57221605997a3cd815f2a9689486abbdb124263fff047ca61068900eb7cb1839

  • monero.freebsd.x64.v0-10-1-0.tar.bz2, 3858d4786b65a37e981b142e9c0f256ac66662314794d05f595c4c30cb5b6ddb

Updating: Wallet Files

Simply create a new directory with the 0.10.1 binaries and copy your wallet files over to there. Make sure to backup your wallet files properly. If you need any help, feel free to PM me or respond in this thread. Note that your wallet contains three files, namely wallet.keys (this is the most important file, since it contains your keys), wallet (this is the wallet cache, which contains your transaction history and private tx keys), and wallet.address (which is just your public address). In addition, if you incur a bug whilst upgrading, you can always restore your wallet with the mnemonic seed as follows:

For Mac and Linux:

./monero-wallet-cli --restore-deterministic-wallet

On Windows make sure to launch it from the command line. Go to the folder monero-cli-wallet is located and make sure your cursor isn't located on any of the files. Subsequently do SHIFT + right click and it will give you an option to "Open command window here". Lastly, type the following command:

monero-wallet-cli.exe --restore-deterministic-wallet

If you want to restore from the private keys instead of the mnemonic seed, replace --restore-deterministic-wallet with --generate-from-keys

Contributors for this Release

This release was the direct result of 29 people who worked, largely unpaid and altruistically, to put out 481 commits containing 10 517 new lines of code. We'd like to thank them very much for their time and effort. In no particular order they are:

  • Randi Joseph

  • Gingeropolous

  • Shen Noether

  • Pierre Boyer

  • taushet

  • guzzi_jones

  • Oyvind Kvanes

  • J Ryan Littlefield

  • lethos3

  • Will Skinner

  • codehalo

  • Jaquee

  • Dan Miller

  • moneromooo-monero

  • AwfulCrawler

  • Lee Clagett

  • Riccardo Spagni

  • zveda

  • anonimal

  • TedTheFicus

  • luigi1111

  • Myagui

  • NanoAkron

  • Jkat

  • iDunk5400

  • Adriaan Joubert

  • Dion Ahmetaj

  • Jacob Brydolf

  • Ilya Kitaev

GUI

You can find the release (and binaries) of the first beta here.

79 comments
99% Upvoted
This thread is archived
New comments cannot be posted and votes cannot be cast
Sort by
level 1
10 points · 3 years ago

Can we add exchanges to the list above also and keep it updated?

I seem to recall that Shapeshift did not upgrade on time last year and claimed they were not informed.

Please ask shapeshift, poloniex, bitfinex, bittrex, bitmex, tuxexchange, bter etc for updates

I think I read that xmr.to and cryptopia were already updated?

level 2
ModeratorOriginal Poster2 points · 3 years ago

I'll add another table :)

level 1
7 points · 3 years ago

adds full support for "fluffy blocks", a propagation improvement similar to Compact Blocks in Bitcoin Core

You mean Xtreme Thinblocks in Bitcoin Unlimited, which was first to implement it.

level 2
ModeratorOriginal Poster2 points · 3 years ago

It's similar. Also, I don't write the release notes. I just copy pasted them.

level 2
XMR Core Team3 points · 3 years ago

No, it's not similar to Xtreme Thinblocks. It is similar to Compact Blocks. The net effect may be similar, but the implementation is quite specific. The discussion around it, from the beginning, was to have an implementation that was similar to Compact Blocks. We have never paid any attention to who got there "first", nor is it relevant.

level 1
3 points · 3 years ago

I have Monero stored in cold storage (created via moneroadress.org) backed up with the 25 word mnemonic seed. Does this update require me to do anything with this wallet?

level 2
ModeratorOriginal Poster2 points · 3 years ago

No :)

level 1
2 points · 3 years ago
level 1
2 points · 3 years ago

also AB /u/trappy_AB and Sigaint

level 1
2 points · 3 years ago

http://xmr.coolpool.io/ is fully upgraded to 0.10.1

level 2
ModeratorOriginal Poster1 point · 3 years ago

Forgot to respond here, my apologies. Added you now.

level 1
1 point · 3 years ago
level 2
ModeratorOriginal Poster1 point · 3 years ago

Updated :)

level 1
1 point · 3 years ago

I still get bus error 10, similar to what I got with the previous release.

I have also updated my OS recently - it didn't change a thing. What happens when I run Monero daemon is this (identifying information omitted with XXXXXXXXX):

Last login: Wed Dec 28 10:40:54 on ttys000 /Users/XXXXXXXXX/Downloads/monero.mac.x64.v0-10-1-0/monerod ; exit;

XXXXXXXXXXXX

/Users/XXXXXXXXX/Downloads/monero.mac.x64.v0-10-1-0/monerod ; exit;

Creating the logger system

2016-Dec-28 10:42:47.538600 Initializing cryptonote protocol...

2016-Dec-28 10:42:47.538749 Cryptonote protocol initialized OK

2016-Dec-28 10:42:47.539035 Initializing p2p server...

2016-Dec-28 10:42:47.835838 Set limit-up to 2048 kB/s

2016-Dec-28 10:42:47.835962 Set limit-down to 8192 kB/s

2016-Dec-28 10:42:47.836020 Set limit-up to 2048 kB/s

2016-Dec-28 10:42:47.836162 Set limit-down to 8192 kB/s

2016-Dec-28 10:42:47.840377 Binding on 0.0.0.0:18080

2016-Dec-28 10:42:47.840644 Net service bound to 0.0.0.0:18080

2016-Dec-28 10:42:47.840695 Attempting to add IGD port mapping.

2016-Dec-28 10:42:51.859277 No IGD was found.

2016-Dec-28 10:42:51.859394 P2p server initialized OK

2016-Dec-28 10:42:51.859586 Initializing core rpc server...

2016-Dec-28 10:42:51.859804 Binding on 127.0.0.1:18081

2016-Dec-28 10:42:51.860059 Core rpc server initialized OK on port: 18081

2016-Dec-28 10:42:51.860192 Initializing core...

2016-Dec-28 10:42:51.862051 Loading blockchain from folder /Users/XXXXXXXXX/.bitmonero/lmdb ...

2016-Dec-28 10:42:51.862130 option: fast

2016-Dec-28 10:42:51.862163 option: async

2016-Dec-28 10:42:51.862190 option: 1000

Bus error: 10

logout

Saving session...

...copying shared history...

...saving history...truncating history files...

...completed.

I have 15 inch mid 2010 Macbook pro, running macOS Sierra 10.12

I don't have any idea why this happens.

level 2
ModeratorOriginal Poster1 point · 3 years ago

I don't have any idea why this happens.

Unfortunately, it might be unrelated to Monero and related to your hardware. This is what MoneroMooo said too.

level 1
1 point · 3 years ago

xmrpool.eu also joined the party. Pool is running monero node 0.10.1 underneath. Also pool code is prepared for ringCT transactions.

level 2
ModeratorOriginal Poster1 point · 3 years ago

I've added you to the list!

level 1
1 point · 3 years ago

MoneroHash is 100% ready for the fork :)

level 2
ModeratorOriginal Poster1 point · 3 years ago

Updated.

More posts from the Monero community
Continue browsing in r/Monero
This is the official subreddit of Monero (XMR), a secure, private, untraceable currency that is open-source and freely available to all.
167k

Members

3.5k

Online


Created Apr 24, 2014