Is it real?
Yes, spellchecking is real. ... In some parts of this planet at least. An so spead 48-50Mkeys/sec!
For that matter already, the LBS also does not find everything, but only from the list given to him. And how much is there given to him? 100K addresses? 200? 300?
I thought I mentioned beyond reasonable doubt: 16M addresses - those that have at least 1 Satoshi on them. Well, well, you can even specify a couple of millions through the bloom filter. But there are currently about 400 million known addresses!
And to check every address on the block, even if your ABD is raised, then the speed will be completely different, much less.
Last time I checked there were 270M known addresses, but maybe that is bigger now. So? People usually don't want to search for empty addresses. For the topic of finding collisions, it would actually be preferable to look up all of them (and an instant speedup factor of ~20) and these proposals have been made. Maybe in the next version of LBC. I don't know what ABD is, sorry. |
|
|
|
English is not my native language and sorry for mistakes.
Rico666 i watch you work long time ago and its so good, but what about bitcrack adoption to your pool ? Why not ? It will have moar power and we can solve puzzel really fast ? I think this is the next stage of bitcoin soon or later pepople will start to brute keys, also im wondering is it possible to adopt fpga cluster to mine keys what do u think ?
Well, first off - if bitcrack did all the work LBC is doing (watching all 16M addresses AND computing compressed and uncompressed addresses), the speed difference would not be that big anymore. The reason people use bitcrack is just because of the usual little greedy minds of the common crypto crowd: quick buck from the puzzle transaction bitcoins. As I mentioned before, with that approach something falls through the cracks and LBC finds what bitcrack misses. Second, I believe I could write (with the help of certain 1-2 people I know) something much faster than bitcrack. Essentially a LBCv2 doing as usual a complete search (all addresses, all privkeys sequentially) - way faster than bitcrack, but I'm working now on bigger things, so LBC has not the priority. |
|
|
|
Why speed at pool is to slow "24h Pool Performance: 233.52 Mkeys/s"? This in one GPU GeForce GTX 1080 TI. Info from here https://bitcointalk.org/index.php?topic=4453897.msg49793258#msg49793258GeForce GTX 1080 TI = compressed = 1030 MKeys/s (with 40k targets)
GeForce GTX 1080 TI = compressed = 350.28 MKeys/s (-b 224 -t 128 -p 1024)
GeForce GTX 1080 TI = compressed = 350.28 MKeys/s
Because in Russia, Large Bitcoin Collider collides you! Different software, different use case, comparing apples and steaks. => Stop making fun of blondies mrxtraf. |
|
|
|
Is there someone who to talk to about License violations? You guys "over there" really think you can start a currency based on license violations? edit: Also, please everyone be very careful about closed source (of GPLv3 software) clones of Burst: https://www.reddit.com/r/burstcoin/comments/c4v1yi/important_boom_coin_scam/Would not be the first time we see some shady things going on from 中文  |
|
|
|
|
It's incredible. They = Devs
1) They violate the GPLv3 - allegedly to not be copied.
Blatantly using Burst source code themselves (but ok, that's what GPLv3 is for), but then worse
2) They are being caught cheating like hell with instamine and 10000x,1000x privileged accounts
In the source they tried to hide.
3) Analysis reveals they grabbed 99.49% of the total supply cheating from 2
As if nothing happened, they relaunch and secure those 11 million Boom in a premine account.
And again they find donkeys who follow the carrot.
Some people simply can't be helped.
|
|
|
|
It is certainly that we will open source, when we make sure there are no fatal security issues...
Translation: we are amateurs. |
|
|
|
Pretty sure you didn't read the thread - maybe message #76 ? |
|
|
|
OP: How you can even think that you do not lose your face by keeping the wallet closed source, just after Boomcoin has been exposed as completely SCAM FRAUD... ===> https://bitcointalk.org/index.php?topic=5147634.msg51589000#msg51589000This happens if you allow a wallet to be closed source!  Newbie account, funny roadmap I mean "completed the white paper". Yeah, I can complete a copy and paste "white paper" also in one evening - if you provide the booze. Is there some sort of contest going on in China right now? Who will shit out the most CPoC (sic!) coins? Also planning on any GPLv3 violation? |
|
|
|
Seriously @OP - you need to relaunch. 1) make it open source. As is, it's illegal. You will encounter constant takedown notices both based on DMCA for the webpage containing the downloads (from fellow US-based copyright holders) or good old EU copyright law. The coin network will not get any node/feet on the ground in US and Europe. Decentral much? Any exchange will be informed about the license breach of the software (and as such not list the coin). You will not be able to use e.g. Github - be it even for binary only releases. etc. etc. Do you really intend to keep up a coin with such a shaky basis? By the way, you also violate the license of the Blago miner. 2) Make at least the fundamentally necessary changes You managed to change the name, but you didn't manage the communication ports 8123 & 8125. Gosh even to the point, where the regular BRS (Burst Reference Software) syncs on your network. A total fuckup. editIn addition: I wrote about the tx increase you'd get free house - make use of it. Also, you couldn't help but premine this coin, well ok. But did you really need to f*ck in there 50k blocks for no other reason than get your premine??? You could simply anchor a transaction with XXX Boom on a certain address (you had the passphrase to) directly in the genesis block - you know? That way not everyone would need to lame-ass sync 50k blocks from behind the great firewall of Yellowmanland. Think about it. |
|
|
|
Fork burstcoin so BHD, "Boom" and the POCC aren't getting a penny of our profits. That goes for our double dipping miner traitors too.
You will need to replot then, because if it's PoC2 mineable, it's Helix mineable too. Which means you need to shoot yourself in the knee first. Be my guest. |
|
|
|
|
Fun fact: Helix mining possible with Boomcoin
|
|
|
|
Dear Guru's. How to set your e-mail address in the arguments of the ./LBC command?
--email <email address>
Give a email address for notifications. You set this and the
server stores that info until you set another. NYI
You know what NYI means? If you want email notification when your client finds something, use the hooks: https://lbc.cryptoguru.org/man/user#hooks |
|
|
|
Meanwhile, the LBC has found a few in between. |
|
|
|
why trust rico666? some even say he killed burst. PoC-Consortium cheated the community. Now they want to charge miners a high fee when using helix. so much for the topic "professional approach"
This thread is about Boomcoin and not about some whackos' perception of reality. "Some even say I eat babies." So what? What I wrote about obligations that the GPLv3 license brings, you can read it up yourself if you "don't trust me" https://www.gnu.org/licenses/quick-guide-gplv3.en.htmlSheesh. I will even paste out the relevant passage for the tl;dr Dyslexion guys out there: Protecting Your Right to Tinker
Tivoization is a dangerous attempt to curtail users' freedom: the right to modify your software will become meaningless if none of your computers let you do it. GPLv3 stops tivoization by requiring the distributor to provide you with whatever information or data is necessary to install modified software on the device. This may be as simple as a set of instructions, or it may include special data such as cryptographic keys or information about how to bypass an integrity check in the hardware. It will depend on how the hardware was designed—but no matter what information you need, you must be able to get it. If I insisted on obtaining the source for Boomcoin now (because I wanted to tinker with it, or even make another clone) and the Boomcoin author(s) would not comply, I could take this to the FSF. --- As per your vomitory about Helix license: Yeah - duh! It's commercial software. We're not charging "high fee", we simply sell licenses for that software. It's not mandatory dummy, it's simply an investment for PoC miners - just cheaper than buying HDDs. "Eulenstein", I do know that it doesn't matter what I write here, you made it perfectly clear in your little text that you are not to be rationalized with. |
|
|
|
Yes. Boom is a code fork of Burst. We will open the source code when the system is more stable.
Well, I am not the FSF, but once again: You do not get to decide that. Once you published Boom (which you did for the TestNet already), you have to publish the source too. The GPLv3 license requires it unconditionally. And not when you decide to do it. Your mode of operation basically is similar to BHD (where the authors also decided to "open the source once the system is stable"). Which means exactly 2-3 things: - You suggest your code is not stable.
- You start out your coin in an illegal way. Please be aware that everyone running a node is subject to ISP take down notices and license violation lawsuits. Now this may not bother you(?) in some anonymous way and behind some great firewall of China, but if you want people to run the nodes in sane jurisdictions, it becomes a problem.
- It may hint to a security by obscurity concept. You believe that you gain security for the coin by obstructing access to the code. In a business such as cryptocurrencies, where strong cryptography and proven mathematical concepts are key, obfuscation is a very weak protection.
|
|
|
|
And while you are at it: https://twitter.com/PoC_Consortium/status/1066770865222750208It is really very easy to ramp up the TPS of this coin, so you should maybe consider changing a few parameters to start out with a much higher TPS. - You could raise the Multi-Out to a comfortable 128 (Burst: 64) and Multi-Out Same to 250 (Burst: 128). I wouldn't go over 255 as that would require a change in the format.
- You could raise the number of possible transactions in a block from 1020 to ... idk ... 2048? and the max Block size from a very understated 175KiB to some 512 KiB.
This should give you something around 500 TPS instead of the max. 80 TPS of Burst. Alternately you could lower the block time to 2 minutes which would make fork resolution still bearable, would improve this coins usage as payment system (confirmation times) and - of course - double the tx capacity. You're welcome. |
|
|
|
The core team is debugging the Boom code. We will open the source code when the system is more stable. Boom has borrowed Burst smart contract, asset issuance, crowdfunding and various features.
This is bullshit. BRS (The Burst Reference Software) is GPLv3. If you "borrowed" code of it, (which you didn't by the way, you simply forked the whole code base and added some own extensions such as PledgeService etc.) then your code is also GPLv3 and withholding the source is a violation of the GPLv3 license. Analyzing your diction, I'd say the "development team" is a weird mixture of BHD guys and some former BurstNation "developers". Maybe you would like to add websockets too?  In any case, using Java which has a nifty bytecode that can be decompiled pretty well proves your GPLv3 license violation, so cut the shit please. --- I'm not against this project per se - any PoC coin instance can be valuable IMHO, but please try to maintain a slightly more professional approach. |
|
|
|
|
Show Posts
