44

Every single piece of security software you run has to try force security updates, otherwise you could be running a trivially compromised piece of software. Most closed-source software, and even open-source software that isn't as sensitive to tampering as Monero, use things like mailing lists to notify you of a new major version. Lots of them also use in-app ...


17

As I understand it the reason for the scheduled forks is to avoid the plight Bitcoin now experiences, where politics trumps tech, and forks are used as a way of derailing features and progress. It also empowers users and miners to regularly choose rather than continually defer to "smarter" people. The forks won't go on forever though, the devs have said ...


15

No reason. Some did just that (probably not intentionally, though). You're free to mine on that chain, I think it's still there. You could make an exchange and sell those monero if you wished (assuming you find buyers). The reason ETC kept going strong is that the ETH fork chose to reach back and blacklist some transactions or outputs (I don't know the ...


15

The message means that your block height is 62 days ahead of a block which you just were told was mined (on top of a block way back in history). As you verified your block height was correct (as of the time of that image) The blocks that you are "62 days ahead" of were created by miners that remained on Monero chain(s) that we hard-forked away from. ...


15

30 days before the fork there will be a code freeze + tag + release, If there are no major changes there will at least be an increase in the protocol version. A similar fork system to Bitcoin will apply, whereby a rollover to the new code after the trigger block will only occur if a sufficient number of miners are running the new code. I am not aware of a ...


15

@Jollymort will probably answer this better but the current dynamic size algorithm didn't work well with RingCT transactions. It worked well with non RingCT transactions, which were smaller. Once a miner has put enough transactions in a block to reach the median size of the last 100 blocks she faces this decision: add one more transaction, which, in case ...


14

The hard fork scehedule is intended to allow Monero to evolve in a regular fashion, while still leaving users enough time to update before being forked away from the network. With scheduled hard forks, there is less friction in deciding whether a change is worth a hard fork or not. There will be a hard fork anyway. The question becomes the simpler one of ...


13

Does it mean that no upgrade will be required prior to RCT HF? This is currently correct. However, Ring CT is also in a testing phase on testnet. Therefore, there exists a possibility that bugs are found that have to be fixed before the v4 fork enables Ring CT transactions on mainnet. If this happens, it would be wise to upgrade your software to the latest ...


11

If by "reject", you mean prevent that transaction from being mined and being available to your private key, then no. If by "reject", you mean only act on rct payments, then you could ask the client for a monero address to return non-rct payment, possibly minus a small fee to cover the tx fee (for instance, I believe shapeshift will return your monero if you ...


11

Is it possible to change the total supply afterwards, by a Hard Fork for example? That would be possible, but it would break the social contract. I am quite certain almost all community members and miners would be opposed to it. Does is prevent the equal distribution of Moneros? Not necessarily. Given that Monero has a tail emission of <1% per year (...


9

Despite the hard fork in March, 2016, setting a minimum mixin and effectively banning dust outputs (except as part of the coinbase, which is further going to change in the September, 2016, hard fork) we provided a "catch" that let users sweep their dust outputs at a mixin of 0. This functionality will be supported indefinitely, because maybe in a few years ...


9

Theres no need to move arround your funds after any fork, even with updates like min mixing and the future RingCT the transactions will allways be compatible with the old ones


9

Miners will lose what they would have gained if the pool had been on the right fork: any block mined on the wrong fork will eventually get reorganized away. If the pool's on the wrong fork, any money from the wrong chain it sends miners will be just that: on the wrong chain. It will therefore only appear in wallets running the wrong chain. This will ...


9

Privacy: Outputs are where amounts of Monero are stored on the blockchain. When you spend one of your outputs in a transaction, it cannot be known which of 7 different source outputs you're really spending. Therefore your anonymity set grows by 40%. Another advantage is that outputs that you receive will now more likely be used as decoys in other people's ...


8

This answer is assuming you are on any 0.9.x version (lower versions would already have been booted off in the previous hardfork) currently. Note that 0.10 is going to be released soon. In general it is advised to use the latest binaries, because they contain bugfixes and new features. What will happen (if anything) to my actual wallet during this ...


8

10.1 has a fix for RingCT. Changes have been made to 10.1 nodes to fork one block before 10.0 in order to avoid letting anyone use the flawed RingCT code, so Miners need to make sure they mine on 10.1 as they need to make sure they include the bugfixed RingCT transactions only, otherwise they will fork themselves off the network. The code changes that result ...


8

The change occured at hard fork 2, on block 1009827 (see the table near the top of src/cryptonote_core/blockchain.cpp). This was in march 2016.


8

There is now a monero-announce mailing list on which such important announcements will be made: https://lists.getmonero.org/postorius/lists/monero-announce.lists.getmonero.org/


7

From the Monero website: Note that the v4 hard fork has been moved to the beginning of January, 2017, although the v5 hard fork remains set at September, 2017. This is to enable early availability of RingCT transactions on the Monero network, although they will not be enforced as the only possible transaction type until the v5 hard fork. The hard fork in ...


7

As of the Monero 0.9.0 Hydrogen Helix release the minimum mixin is 2 (2 foreign outputs per ring for a total of 3) with the exception of dust transactions. The minimum mixin will be raised to 4 in a future fork probably at the same time as RingCT according to discussions from the most recent developer meeting. The numbers above along with the simplewallet ...


7

First, some background. In MRL-0005 - Ring Confidential Transactions there's a section on range proofs, relevant quotes below. 5 Aggregate Schnorr Range Proofs In [11], the confidential transactions without ring signatures uses a type of ring signature based on [1] called a Borromean ring signature, which helps to prove a committed value lies ...


7

Let's first define the terms: Hardfork means that nodes running old and new software will have a diverging view of the blockchain. They'll be on their own fork, playing by different rules. Softfork means that even though nodes running old and new software have a different view of the blockckhain the blockchain doesn't fork. Let's now take RingCT (RCT) as ...


7

The change was introduced with the Monero v0.9.0 "Hydrogen Helix" release on the 1st of Jan, 2016 however it did not take effect until the 20th of March, 2016 at block 1009827 as explained by user3603. More details about the original Hydrogen Helix release can be found here


7

The v6 fork is planned for block 1400000, which is on or about the 16th of september. Hash rate increase had little effect on the projected date, as can be seen in the patch (https://github.com/monero-project/monero/pull/2335/commits/2147859ac9d4660d0cc7736c8524fb2b48e9fbb2), so the discussion above is incorrect. Apparently the 21 date comes from a note in ...


7

In versions 1 to 6 of the protocol, the CryptoNight algorithm was very roughly: state = keccak(block_data) scratchpad = fill_scratchpad(state) loop 524,288 times address = compute_address(scratchpad, state) modification1(scratchpad, address) address = compute_address(scratchpad, state) modification2(scratchpad, address) text = reduce(scratchpad, ...


6

When someone uses a rct transaction, the outputs are necessarily rct. From hard fork 4 (expected in or around march 2017), both rct and non rct transactions will be permitted. From hard fork 5 (expected in or around september 2017), non rct transasctions will be permitted only if they are spending unmixable outputs (ie, the rules for allowing mixin 0 now). ...


6

If you knew the exact transaction ID, and you got most of the network to implement an emergency hard fork, you could roll back to the block before that transaction and then blacklist that particular transaction ID. You would probably not affect too much by doing this, assuming it was done quickly enough (like within a couple of hours). I doubt that this sort ...


6

Block 1406997 doesn't come for 341.5 days (as of this writing, Oct 19th, 2016, at block 1161101). September 25th of 2017 seems a bit...much. Please correct my errors. (I would have posted as a comment to the answer above, but my rating on stackoverflow is too low. You could help by up-voting me, just for trying to be constructive.)


Only top voted, non community-wiki answers of a minimum length are eligible