Spekulatius
Legendary
Offline
Activity: 1022
Merit: 1000
|
|
May 24, 2014, 11:39:13 PM |
|
|
|
|
|
KeyserSozeMC
|
|
May 24, 2014, 11:42:16 PM |
|
|
Hey, smexy. Don't waste your time. Time's precious.
|
|
|
Spekulatius
Legendary
Offline
Activity: 1022
Merit: 1000
|
|
May 25, 2014, 02:44:11 AM |
|
Blockchain-based hash: unlike Bytecoin PoW hash, which works on 2MB scratchpad and takes avr 400 ms, new hash will work on blockchain random data to provide operation speed. It gives faster synchronization with network and immunity from DoS attacks. So how usefull is that innovation really and how vulnerable is it in comparison to traditional approaches? Cant the supposedly random data from the blockchain be precalculated because, well its already there and not changing much with every new block? Im no techie, so pls have mercy on me
|
|
|
|
33zer0w0lf
|
|
May 25, 2014, 02:53:12 AM |
|
any pools yet? still working on that.
|
|
|
|
btc-mike
|
|
May 25, 2014, 04:37:59 AM |
|
I found a block!!
I have about 500kh/s but 200kh/s of that is not 24/7.
|
|
|
|
mozurt
|
|
May 25, 2014, 08:28:32 AM |
|
how to install wallet in Slitaz?
is there a tutorial for it?
iam newbie thanks
|
|
|
|
otila
|
|
May 25, 2014, 08:49:36 AM |
|
how to install wallet in Slitaz?
I heard about Slitaz first time now. Do as the README.md instructs, and see how it goes.
|
|
|
|
michael_phelps
|
|
May 25, 2014, 09:32:36 AM |
|
Hello
How do I set a rpcuser and rpcpassword?
Is it the same as other coins? i.e. Make a boolberry.conf in the roaming folder ?
thanks
|
|
|
|
digicoin
Legendary
Offline
Activity: 1106
Merit: 1000
|
|
May 25, 2014, 09:38:51 AM |
|
any pools yet? still working on that. Hi, Do you store the source code at github.com?
|
|
|
|
azhago
|
|
May 25, 2014, 09:42:35 AM |
|
there is now a cpu miner optimised for MRO (minerd) Any chance he can work with boolb, or to see an optimized miner ?
|
|
|
|
otila
|
|
May 25, 2014, 09:55:54 AM |
|
there is now a cpu miner optimised for MRO (minerd)
It uses AES, boolberry does not. There was a lot to optimize, indeed, they had probably the world's slowest implementation of AES.
|
|
|
|
eddywise
Sr. Member
Offline
Activity: 253
Merit: 250
Let's Boolberry
|
|
May 25, 2014, 09:59:27 AM |
|
there is now a cpu miner optimised for MRO (minerd)
It uses AES, boolberry does not. There was a lot to optimize, indeed, they had probably the world's slowest implementation of AES. I dont think an optimize miner is better If we all rise the hash,so we rise the diff are you guys do see the problem?
|
Boolberry : @eddywise DRK: XqTbkj1hpCWBpBSvbWtzBRu5PxzJ2KoA3F BTC: 1FZYvzY4cPLwwZmU8rGPM7xGYjfjiZUmuZ Once desperately want, now desperate to forget
|
|
|
otila
|
|
May 25, 2014, 10:30:27 AM |
|
there is now a cpu miner optimised for MRO (minerd)
It uses AES, boolberry does not. There was a lot to optimize, indeed, they had probably the world's slowest implementation of AES. I dont think an optimize miner is better If we all rise the hash,so we rise the diff are you guys do see the problem? If all use the optimized miner, all still find same amount of blocks.
|
|
|
|
crypto_zoidberg (OP)
|
|
May 25, 2014, 11:06:36 AM |
|
Blockchain-based hash: unlike Bytecoin PoW hash, which works on 2MB scratchpad and takes avr 400 ms, new hash will work on blockchain random data to provide operation speed. It gives faster synchronization with network and immunity from DoS attacks. So how usefull is that innovation really and how vulnerable is it in comparison to traditional approaches? Cant the supposedly random data from the blockchain be precalculated because, well its already there and not changing much with every new block? Im no techie, so pls have mercy on me With traditional approach, increasing scratchpad leads to increasing time for hash calculation, since hash have to cover all scratchpad memory, to avoid precalculations. Slow PoW hash can lead to pretty big amount of problems, such as weastimg resources with calculating fake PoW, long synchronization, e.t.c. At the other hand, even pretty big fixed scratchpad (2mb for example) doesn't grant that hardware will not move to this area(remember litecoin, they was counted on it, but now they explaining that ASICs is not so bad). Research of other PoW approaches, based on asymmetric memory consuming algorithms (ethereum dagger, Cuckoo Cycle) showed me that there always some risk that algorithm could be reinvented and PoW may become unsuitable(for ex reinvented algo may request few memory). I've just tried to make a step back and look for another way, i want to have one hash operation fast and strong, but i want to have mining process memory hard, because it seems to be great protection from ASIC. I chose scratchpad memory increasing speed that gives enough protection(and even with extra margin for future) but at the same time make able to implement SPV client or mobile version without any problems. It's pretty new approach as i know, well, we'll see how things go. Feel free to contact me if you have any questions.
|
|
|
|
crypto_zoidberg (OP)
|
|
May 25, 2014, 11:19:41 AM Last edit: May 25, 2014, 01:32:40 PM by crypto_zoidberg |
|
It uses AES, boolberry does not. There was a lot to optimize, indeed, they had probably the world's slowest implementation of AES.
Friends, want to say few words about optimized miner.When we had a peak few days ago i suspected that some GPU miner was secretly implemented. But i've contacted with miners that was behind this peak - it was actually a big players with huge power. As far as i know, at this moment there are no optimized or GPU miner. Scratchpad is about 2Mb already and 64bit mul in hash probably make this function is not very attrative for GPU. But anyway, soon as i'll see any optimized hash i'll put it into repo. Peace!
|
|
|
|
aikklond
Legendary
Offline
Activity: 1148
Merit: 1000
|
|
May 25, 2014, 11:24:07 AM |
|
It uses AES, boolberry does not. There was a lot to optimize, indeed, they had probably the world's slowest implementation of AES.
Friends, want to say few words about optimized miner.When we had a peak few days ago i suspected that some GPU hash was secretly implemented. But i've contacted with miners that was behind this peak - it was actually a big players with huge power. As far as i know, at this moment there are no optimized or GPU miner. Scratchpad is about 2Mb already and 64bit mul in hash probably make this function is not very attrative for GPU. But anyway, if soon as i'll see any optimized hash i'll put it into repo. Peace! I think an optimized miner is not so important, on the other hand a pool is important.
|
|
|
|
wxyzups
|
|
May 25, 2014, 11:42:33 AM |
|
Use the official tool INTER-CPU, 30 core. 6 hours nothing Normal right
|
|
|
|
sixteendigits
|
|
May 25, 2014, 11:58:26 AM |
|
Use the official tool INTER-CPU, 30 core. 6 hours nothing Normal right
I'm mining with 7 threads on an 8320 on my GPU mining rig, and 3 threads on the i5-3570k on my desktop. After 24 hours found 2 blocks, so give it time.
|
|
|
|
sixteendigits
|
|
May 25, 2014, 12:00:33 PM |
|
Blockchain-based hash: unlike Bytecoin PoW hash, which works on 2MB scratchpad and takes avr 400 ms, new hash will work on blockchain random data to provide operation speed. It gives faster synchronization with network and immunity from DoS attacks. So how usefull is that innovation really and how vulnerable is it in comparison to traditional approaches? Cant the supposedly random data from the blockchain be precalculated because, well its already there and not changing much with every new block? Im no techie, so pls have mercy on me With traditional approach, increasing scratchpad leads to increasing time for hash calculation, since hash have to cover all scratchpad memory, to avoid precalculations. Slow PoW hash can lead to pretty big amount of problems, such as weastimg resources with calculating fake PoW, long synchronization, e.t.c. At the other hand, even pretty big fixed scratchpad (2mb for example) doesn't grant that hardware will not move to this area(remember litecoin, they was counted on it, but now they explaining that ASICs is not so bad). Research of other PoW approaches, based on asymmetric memory consuming algorithms (ethereum dagger, Cuckoo Cycle) showed me that there always some risk that algorithm could be reinvented and PoW may become unsuitable(for ex reinvented algo may request few memory). I've just tried to make a step back and look for another way, i want to have one hash operation fast and strong, but i want to have mining process memory hard, because it seems to be great protection from ASIC. I chose scratchpad memory increasing speed that gives enough protection(and even with extra margin for future) but at the same time make able to implement SPV client or mobile version without any problems. It's pretty new approach as i know, well, we'll see how things go. Feel free to contact me if you have any questions. So, is this the advantage it has over MRO? Just started digging into this cryptonote tech in the past day, so this is all pretty much greek to me still.
|
|
|
|
otila
|
|
May 25, 2014, 12:02:05 PM |
|
and 3 threads on the i5-3570k on my desktop.
Why not 4?
|
|
|
|
|