Topic: [XMR] Monero - A secure, private, untraceable cryptocurrency - page 703. (Read 4670673 times)

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:

Total hashrate with Claymore version:

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

Damn, that is nice!

From the release info:


Try sync from scratch first:)

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


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

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

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

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



OK, let's convert the blockchain...



 

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.

All good then. Happy to help.

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. 

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


You are on the normal network, not a testnet.


Self explanatory


Amount of mining on the network (approximate)


Current protocol version being used


I'm not actually sure what this one means


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.


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

Outgoing / Incoming connections.

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.

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.

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.

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.




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.

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.

Thanks, forgot that one, but added it above.

I agree it is a valid question, just posted a general remark. Wolf's miner development is nearly done as far as I know, his unofficial (not pushed on github yet) miner even outperforms that of claymore if I recall correctly. Also, I think tewinget is doing or did some work on cleanup and documentation.

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.