Topic: IOTA - page 705. (Read 1473233 times)
In case anyone has noticed my comments regarding a C# address generator, I've created the C# address creator which could be used for a vanity gen. This was created by copying and modifying the JS & Java code with only minimal modifications. On my machine, this creates ~20 (yes, 20) addresses a second, and I've even added a little parallel execution into the process. It's all of the loops embedded within loops that CfB has created....
I'm going to have to study what you guys are doing in order to optimize this. Regardless, even a 100x improvement in address generation will mean that vanitygens won't be reliable for searching for more than 3-4 characters at the beginning of an address.
Oh well, c'est la vie.
I'm going to have to study what you guys are doing in order to optimize this. Regardless, even a 100x improvement in address generation will mean that vanitygens won't be reliable for searching for more than 3-4 characters at the beginning of an address.
Oh well, c'est la vie.
SaM hashing is done @ approximately 30 kH/s rate on an average CPU (Java version). Address generation requires at least 27*27+9=738 hashes. This gives 30000/738=40 addresses per second.
Yes, but I've not posted it to my git account. I'll post it when it's cleaned up a bit coz my first-pass work is always cobbled together with spit and duct tape. I like to just make stuff work, first, and polish later. 
I do have a couple of vanitygens there:
https://github.com/rhartness
I do have a couple of vanitygens there:
https://github.com/rhartness
In case anyone has noticed my comments regarding a C# address generator, I've created the C# address creator which could be used for a vanity gen. This was created by copying and modifying the JS & Java code with only minimal modifications. On my machine, this creates ~20 (yes, 20) addresses a second, and I've even added a little parallel execution into the process. It's all of the loops embedded within loops that CfB has created....
I'm going to have to study what you guys are doing in order to optimize this. Regardless, even a 100x improvement in address generation will mean that vanitygens won't be reliable for searching for more than 3-4 characters at the beginning of an address.
Oh well, c'est la vie.
I'm going to have to study what you guys are doing in order to optimize this. Regardless, even a 100x improvement in address generation will mean that vanitygens won't be reliable for searching for more than 3-4 characters at the beginning of an address.
Oh well, c'est la vie.
It's great to have a vanitygen. Keep us updated.
Do you have a git ?
In case anyone has noticed my comments regarding a C# address generator, I've created the C# address creator which could be used for a vanity gen. This was created by copying and modifying the JS & Java code with only minimal modifications. On my machine, this creates ~20 (yes, 20) addresses a second, and I've even added a little parallel execution into the process. It's all of the loops embedded within loops that CfB has created....
I'm going to have to study what you guys are doing in order to optimize this. Regardless, even a 100x improvement in address generation will mean that vanitygens won't be reliable for searching for more than 3-4 characters at the beginning of an address.
Oh well, c'est la vie.
I'm going to have to study what you guys are doing in order to optimize this. Regardless, even a 100x improvement in address generation will mean that vanitygens won't be reliable for searching for more than 3-4 characters at the beginning of an address.
Oh well, c'est la vie.
5 reasons you’ll embrace digital transformation in 2016
Quote
To be truly transformed, companies must go beyond window dressing the customer experience, embedding a few sensors to monitor production, and monetizing a service with digital technology. They must reach deep into the bare bones of the company, going as far as human resources and finance and as high up as the executive boardroom.
A little update:
Tomorrow I'm going to complete refactoring the code and writing the comments, after that I'll send back-end code to those who offered to do the review.
Front-end won't be ready by Xmas, because we decided to rewrite it completely - first impression is very important (and also iotas won't be claimed till that date anyway).
I stripped out code that decides which tangle tips to extend, during beta phase all nodes will work with help of a special "coordinator" node, this solves problem of someone cloning Iota right away. After the release coordination can be disabled (it's up to a node operator), we will still be running the coordinator, it's necessary to protect Iota until it gets enough hashing power.
Tomorrow I'm going to complete refactoring the code and writing the comments, after that I'll send back-end code to those who offered to do the review.
Front-end won't be ready by Xmas, because we decided to rewrite it completely - first impression is very important (and also iotas won't be claimed till that date anyway).
I stripped out code that decides which tangle tips to extend, during beta phase all nodes will work with help of a special "coordinator" node, this solves problem of someone cloning Iota right away. After the release coordination can be disabled (it's up to a node operator), we will still be running the coordinator, it's necessary to protect Iota until it gets enough hashing power.
Very nice! Good job so far, IOTA will be BIG!
A little update:
Tomorrow I'm going to complete refactoring the code and writing the comments, after that I'll send back-end code to those who offered to do the review.
Front-end won't be ready by Xmas, because we decided to rewrite it completely - first impression is very important (and also iotas won't be claimed till that date anyway).
I stripped out code that decides which tangle tips to extend, during beta phase all nodes will work with help of a special "coordinator" node, this solves problem of someone cloning Iota right away. After the release coordination can be disabled (it's up to a node operator), we will still be running the coordinator, it's necessary to protect Iota until it gets enough hashing power.
Tomorrow I'm going to complete refactoring the code and writing the comments, after that I'll send back-end code to those who offered to do the review.
Front-end won't be ready by Xmas, because we decided to rewrite it completely - first impression is very important (and also iotas won't be claimed till that date anyway).
I stripped out code that decides which tangle tips to extend, during beta phase all nodes will work with help of a special "coordinator" node, this solves problem of someone cloning Iota right away. After the release coordination can be disabled (it's up to a node operator), we will still be running the coordinator, it's necessary to protect Iota until it gets enough hashing power.
A little update:
Tomorrow I'm going to complete refactoring the code and writing the comments, after that I'll send back-end code to those who offered to do the review.
Front-end won't be ready by Xmas, because we decided to rewrite it completely - first impression is very important (and also iotas won't be claimed till that date anyway).
I stripped out code that decides which tangle tips to extend, during beta phase all nodes will work with help of a special "coordinator" node, this solves problem of someone cloning Iota right away. After the release coordination can be disabled (it's up to a node operator), we will still be running the coordinator, it's necessary to protect Iota until it gets enough hashing power.
Tomorrow I'm going to complete refactoring the code and writing the comments, after that I'll send back-end code to those who offered to do the review.
Front-end won't be ready by Xmas, because we decided to rewrite it completely - first impression is very important (and also iotas won't be claimed till that date anyway).
I stripped out code that decides which tangle tips to extend, during beta phase all nodes will work with help of a special "coordinator" node, this solves problem of someone cloning Iota right away. After the release coordination can be disabled (it's up to a node operator), we will still be running the coordinator, it's necessary to protect Iota until it gets enough hashing power.
How/When do we collect our IOTAs? I have never been involved in a presale before and don't really know what I'm doing. 
Great job guys, look forward to seeing where this goes.
do not worryGreat job guys, look forward to seeing where this goes.
there will be an update
My best congratulations. There is so much work to do, the community support is significant and it is necessary.
Indeed.
Everyone that wants to participate in making IOTA grow, send me a PM with your email and skills and I'll invite you into our Ryver!
Really great job guys!!
Well done.
This is the start of a new era.
Can someone explain in "tangle for dummies" terms how Iota is quantum resistant and how Bitcoin is not?
Well done.
This is the start of a new era.
Can someone explain in "tangle for dummies" terms how Iota is quantum resistant and how Bitcoin is not?
Thanks!
This should help: https://bitscan.com/articles/all-about-iota-ii-the-tangle-and-quantum-resistant-cryptography
I don't think the paper would be discussing a 30 fold increase in qubits.
More likely they discussed an extra 30 qubits.
More likely they discussed an extra 30 qubits.
I took the worst-case scenario, e.g. from 10 to 300 qubits. In your case the same effect is achieved with 10 -> 40 transition.
Is IOTA connected with nxthaus in any way? I believe David was involved with that project but can't find any current info on nxthaus. Will iota be traded on that exchange?
Not connected at all and I was only peripherally involved in getting a fiat gateway setup. I have spoken with the team and they consider adding it
You didn't prove any point. You just vaguely alluded that since QC can do many computations in superposition, that it must somehow speedup Cuckoo Cycle finding.
Is it what was written in that paper? That by increasing number of qubits 30-fold number of computations done within the same timeframe is increased 1'000'000'000-fold?
I don't think the paper would be discussing a 30 fold increase in qubits.
More likely they discussed an extra 30 qubits.
For some very particular computation, like integer factoring,
an extra 30 qubits allow you to factorize a number that has 15 more bits.
(http://arxiv.org/abs/quant-ph/0205095 showed a Circuit for Shor's algorithm using 2n+3 qubits).
So in that case you have 2^15 more states in superposition.
When is the launch?
Beta: soon. Waiting for reviews and nodes. Christmas now, so development will naturally be slightly lower than previous, then full launch in January as planned.
Jump to: