[XMR] Monero - A secure, private, untraceable cryptocurrency

[smooth]

There was no fucking attack, it was just a bug!

Yes it was a bug that allowed the v2 block to enter the blockchain too soon. The code was exploited not attacked and this caused the network consensus to fail and split into several blockchains. There needn't be any debate on what happened. A bug was at fault not an attacker.

That is incorrect.  A malicious party crafted a v2 block causing the split so in essence there was an attack, that block did not come about on its own.  This was possible due to a bug in the code which allowed a v2 block to be crafted at this point in time.

100% of attacks take this form. Some code (or occasionally hardware) processes input in a manner that was not intended which makes it exploitable, and a malicious party identifies that input and submits it to carry out the attack. Nothing unusual here.

[Drhiggins]

Can someone explain this to me.

So when you type in status in the daemon you get back something like this:

Height: 914318/914318 (100.0%) on mainnet, not mining, net hash 10.06 MH/s, v1,
up to date, 8+0 connections

So what do the last two numbers mean?  8+0 in this case. 

I notice that number changes if I type in status again.  Is this a real time connection that is being reported back and what does each number represent exactly?

Thanks for any clarity.

[wpalczynski]

Can someone explain this to me.

So when you type in status in the daemon you get back something like this:

Height: 914318/914318 (100.0%) on mainnet, not mining, net hash 10.06 MH/s, v1,
up to date, 8+0 connections

So what do the last two numbers mean?  8+0 in this case.  

I notice that number changes if I type in status again.  Is this a real time connection that is being reported back and what does each number represent exactly?

Thanks for any clarity.

Outgoing / Incoming connections.

[smooth]

Height: 914318/914318 (100.0%)

Blocks your node has relative to the blocks reported by your peers

on mainnet

You are on the normal network, not a testnet.

not mining

Self explanatory

net hash 10.06 MH/s

Amount of mining on the network (approximate)

v1

Current protocol version being used

up to date

I'm not actually sure what this one means

8+0 connections

8 outgoing connections, 0 incoming connections. The latter probably means your incoming port is blocked, but not necessarily. Your node will still function but it is better if you open the port.

I notice that number changes if I type in status again.  Is this a real time connection

Yes the numbers reported will change depending on the 'status' of your node.

[Drhiggins]

I do get incoming. I see them reported as 8+3 or varying values at the time of inquiry.   18080 is open for business.  Thanks for the break down smooth. 

[smooth]

I do get incoming. I see them reported as 8+3 or varying values at the time of inquiry.   18080 is open for business.  Thanks for the break down smooth. 

All good then. Happy to help.

[smooth]

Thanks smooth, can you link tewinget's work please?

Maybe complete, maybe not. Github search is a pain and I'm not so expert with it

https://github.com/monero-project/bitmonero/pulls?page=1&q=is%3Apr+is%3Aclosed+author%3Atewinget

A suggestion: You might consider crafting a funding proposal for the position you think needs to be added. When people suggest that you "do something" instead of just bitching, that doesn't necessarily mean you do the coding yourself or you fill whatever other non-coding roles you think are needed yourself. It could just be initiative to make it happen.

I welcome your feedback in any case.

[Rabinovitch]

OK, it's time to upgrade my monero software...



OK, let's convert the blockchain...



 

[dEBRUYNE]

Thanks smooth, can you link tewinget's work please?

Maybe complete, maybe not. Github search is a pain and I'm not so expert with it

https://github.com/monero-project/bitmonero/pulls?page=1&q=is%3Apr+is%3Aclosed+author%3Atewinget

A suggestion: You might consider crafting a funding proposal for the position you think needs to be added. When people suggest that you "do something" instead of just bitching, that doesn't necessarily mean you do the coding yourself or you fill whatever other non-coding roles you think are needed yourself. It could just be initiative to make it happen.

I welcome your feedback in any case.

More info and comments here -> https://forum.getmonero.org/9/work-in-progress/2373/documentation-and-cleanup-of-source-code

[dEBRUYNE]

OK, it's time to upgrade my monero software...



OK, let's convert the blockchain...



 

Better to sync from scratch, it's way faster than converting the blockchain. Furthermore, I think there were some minor bugs with converting the blockchain which could result in getting an error (such as in your case).

[dEBRUYNE]

It seems like Shen is going full steam ahead! Some updates regarding Ring Confidential Transactions for Monero:

edit 1/9/2016: Looks like its fully funded! Thanks to everyone who funded - I've started the work (https://github.com/ShenNoether/MiniNero/commit/9ede58897808bee784dab296654b99899a58c109), and I will be posting updates here for the next two weeks as I work on this, rather than updating both here and the stickied reddit post.

edit 1/13/2016: MG sigs + demo are done (git clone https://github.com/ShenNoether/MiniNero.git, cd brief, make, a.exe (or a.out depending on system)). Most of the helper functions are there, so the rest should go a little bit quicker. Also fixed a tiny bug in Monero's keccak function.

edit 1/14/2016: ASNL + demo are done. (https://github.com/ShenNoether/MiniNero/commit/88b2d93e137bd5a2e2a2700ac11136705bd463c5) I will probably do some additional checks on these and the MG sigs once I get everything finished, however they are working as expected now.

edit 1/15/2016: spent an all nighter getting a rough version of all the code finished - I will most likely clean it up, and then make it available early next week.

https://forum.getmonero.org/8/funding-required/2450/ring-ct-c-crypto

[fluffypony]

OK, it's time to upgrade my monero software...

OK, let's convert the blockchain...

 

From the release info:

It is highly recommended that you delete the contents of your Monero working directory and sync from scratch. This directory can be found in ~/.bitmonero on Linux and OS X, and on Windows in \Users\username\AppData\Roaming\bitmonero or \ProgramData\bitmonero.

Syncing from scratch is EXTREMELY fast in this version, pretty much at bittorrent speeds, and will leave you with a fully verified blockchain.

Alternatively: if you want to grab the bootstrap (NOTE: there is a new bootstrap format!) off the website then you can get it at https://downloads.getmonero.org/blockchain.raw - once downloaded you can import it with blockchain_import --input-file /path/to/your/download.raw. If you're particularly brave you can pass the --verify 0 flag to skip verification during import.

If you REALLY want to convert your old blockchain: you can either use the blockchain_converter tool, or you can use blockchain_export to create a blockchain.raw, followed by blockchain_import to import it into the new LMDB format.

Try sync from scratch first:)

[QuantumQrack]

It seems like Shen is going full steam ahead! Some updates regarding Ring Confidential Transactions for Monero:

edit 1/9/2016: Looks like its fully funded! Thanks to everyone who funded - I've started the work (https://github.com/ShenNoether/MiniNero/commit/9ede58897808bee784dab296654b99899a58c109), and I will be posting updates here for the next two weeks as I work on this, rather than updating both here and the stickied reddit post.

edit 1/13/2016: MG sigs + demo are done (git clone https://github.com/ShenNoether/MiniNero.git, cd brief, make, a.exe (or a.out depending on system)). Most of the helper functions are there, so the rest should go a little bit quicker. Also fixed a tiny bug in Monero's keccak function.

edit 1/14/2016: ASNL + demo are done. (https://github.com/ShenNoether/MiniNero/commit/88b2d93e137bd5a2e2a2700ac11136705bd463c5) I will probably do some additional checks on these and the MG sigs once I get everything finished, however they are working as expected now.

edit 1/15/2016: spent an all nighter getting a rough version of all the code finished - I will most likely clean it up, and then make it available early next week.

https://forum.getmonero.org/8/funding-required/2450/ring-ct-c-crypto

Damn, that is nice!

[jwinterm]

New build of Wolf miner on Win10 using a 270 and 7950 with stock clocks (1080/1400 and 925/1250, respectively) and driver version 15.30:

Code:

[12:36:06] Share accepted: 9/9 (100.00%)
[12:36:06] Total Hashrate: 759.68H/s
[12:36:07] Thread 1, GPU ID 1, GPU Type: Tahiti: 411.24H/s
[12:36:08] Thread 0, GPU ID 0, GPU Type: Pitcairn: 347.20H/s
[12:36:09] Thread 1, GPU ID 1, GPU Type: Tahiti: 406.03H/s
[12:36:12] Thread 1, GPU ID 1, GPU Type: Tahiti: 411.58H/s
[12:36:12] Thread 0, GPU ID 0, GPU Type: Pitcairn: 348.14H/s

Total hashrate with Claymore version:

Code:

Speed: 837 h/s, TotalHashes: 133K, DevHashes: 2K Mining time: 00:02

So, ~10% lower hashrate with Wolf's new version.

[iDunk]

~390H/s on a 270X  1125/1500, ri/ws: 672/8

http://imgur.com/1l8zUP6

[aerbax]

It seems like Shen is going full steam ahead! Some updates regarding Ring Confidential Transactions for Monero:
....

I'm curious...

Let's pretend Shen completes RingCT at the end of next week...Semi-production or something like a RC. 

Would this be code that we could expect to be implemented in a point release?  Could we see it go live before the hard fork?  Or would this be post-hard-fork and pre-the-next-hard-fork?

[smooth]

No it is not going to go in before the next fork. It would need a fork to support the new signature method.

[GingerAle]

New build of Wolf miner on Win10 using a 270 and 7950 with stock clocks (1080/1400 and 925/1250, respectively):

Code:

[12:36:06] Share accepted: 9/9 (100.00%)
[12:36:06] Total Hashrate: 759.68H/s
[12:36:07] Thread 1, GPU ID 1, GPU Type: Tahiti: 411.24H/s
[12:36:08] Thread 0, GPU ID 0, GPU Type: Pitcairn: 347.20H/s
[12:36:09] Thread 1, GPU ID 1, GPU Type: Tahiti: 406.03H/s
[12:36:12] Thread 1, GPU ID 1, GPU Type: Tahiti: 411.58H/s
[12:36:12] Thread 0, GPU ID 0, GPU Type: Pitcairn: 348.14H/s

Total hashrate with Claymore version:

Code:

Speed: 837 h/s, TotalHashes: 133K, DevHashes: 2K Mining time: 00:02

So, ~10% lower hashrate with Wolf's new version.

Is that the unreleased one he's waiting to release? It's gotta be.

[fluffypony]

No it is not going to go in before the next fork. It would need a fork to support the new signature method.

Just to reiterate - the idea is to code-freeze 7 months before the hard fork. This time we didn't code freeze as timeously as we would have liked, but even if you grabbed the code from like October you'd still be fine till after the March fork. Even the malicious fork from Friday wouldn't have affected you, as long as you gave it a few days for the fork to resolve.

[smooth]

No it is not going to go in before the next fork. It would need a fork to support the new signature method.

Just to reiterate - the idea is to code-freeze 7 months before the hard fork. This time we didn't code freeze as timeously as we would have liked, but even if you grabbed the code from like October you'd still be fine till after the March fork. Even the malicious fork from Friday wouldn't have affected you, as long as you gave it a few days for the fork to resolve.

More like a few hours even due to the hard work of the real developers. I was helping by drinking whiskey.