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

[Hueristic]

...

We got added a while ago lol -> https://www.cryptsy.com/markets/view/XMR_BTC

Also, as a general remark to your post, bear in mind that most people working on Monero are merely volunteers and got day jobs, and/or companies to run as well. Therefore, their time is mostly limited. On top of that, resources are kind of limited.

LOL, never even noticed. Finding the Craptsy drama hilarious. It's not like this forum hasn't been warned for at least a year.

I realize that the Devs are volunteers, if not I would have really come down ages ago. This scene is not even remotely operated in a professional manner. This is more a sign of disorganization as opposed to one of incompetence. I think sometimes the scope of this project is forgotten. This project sits on a razors edge and can go either way. The organizational structure is fine for a project that is not trying to change the world but this project is held to higher standards and rightly so. All funding requests for the roadmap have been met as far as I've seen and if another position is needed then it is the devs job to bring that up to the community. We are sitting on the outside with not much more than faith and pull requests. AFA the chant "Shutup if your not contributing" that is a nothing but a Ad hominen. Contributing comes in many forms, time is not the least of which. The barriers to entry for coding this coin look intentionally conflated. The first thing a project manager is going to do when starting or taking on a project is to check the documentation and that includes the logic tree which I asked for over a year ago and still have yet to see. Commenting code is not a substitute for a simple flowchart.

BTW I just got rivered (poker) for a butt-ton so I'm pissy at the moment.

I think the question on who is active is valid.

In addition to the commits you see on github (mostly moneromooo, fluffypony, recently some from hyc, occ. others), other people regularly involved with testing, code reviews, debugging, and design decisions are myself, warptangent, tacotime, luigi, and othe, plus occ. others. Shen is actively developing the ringCT stuff (currently working on C++ code for it). NoodleDoodle does, well, whatever amazing things he feels like doing such as a the massive optimization rework that took months. He seems to prefer working independently. Wolf recently did some miner development but I think that is winding down. Finally, tewinget is doing or did some work on cleanup and documentation.

All are welcome.

EDIT: added tewinget's cleanup and documentation work.

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


Again, bad day all around so I'm being a bit of a dick, I know it but sometimes someone has to be the one to say the emperor is not wearing cloths.

[wpalczynski]

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.

[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.