Pages:
Author

Topic: [ANN]DEFT First crypto utilizing the balloon hash, new memory hard algo - page 15. (Read 35991 times)

newbie
Activity: 6
Merit: 0
Hm, have problem with compiling on ubuntu 16.04:

Code:
  CXXLD    deftd
/usr/bin/ld: libbitcoin_consensus.a(libbitcoin_consensus_a-balloon.o): relocation R_X86_64_PC32 against undefined symbol `SHA256_Init@@OPENSSL_1.0.0' can not be used when making a shared object; recompile with -fPIC
/usr/bin/ld: final link failed: Bad value
collect2: error: ld returned 1 exit status
Makefile:3641: recipe for target 'deftd' failed
make[2]: *** [deftd] Error 1

Can dev to fix this? Please.

can you do a git pull and recompile again? issue should be resolved, apologies..

Yes, it successful compiled now. Thanks, mate!
newbie
Activity: 53
Merit: 0
newbie
Activity: 65
Merit: 0
hero member
Activity: 636
Merit: 516
Hm, have problem with compiling on ubuntu 16.04:

Code:
  CXXLD    deftd
/usr/bin/ld: libbitcoin_consensus.a(libbitcoin_consensus_a-balloon.o): relocation R_X86_64_PC32 against undefined symbol `SHA256_Init@@OPENSSL_1.0.0' can not be used when making a shared object; recompile with -fPIC
/usr/bin/ld: final link failed: Bad value
collect2: error: ld returned 1 exit status
Makefile:3641: recipe for target 'deftd' failed
make[2]: *** [deftd] Error 1

Can dev to fix this? Please.

can you do a git pull and recompile again? issue should be resolved, apologies..
hero member
Activity: 636
Merit: 516
Hm, have problem with compiling on ubuntu 16.04:

Code:
  CXXLD    deftd
/usr/bin/ld: libbitcoin_consensus.a(libbitcoin_consensus_a-balloon.o): relocation R_X86_64_PC32 against undefined symbol `SHA256_Init@@OPENSSL_1.0.0' can not be used when making a shared object; recompile with -fPIC
/usr/bin/ld: final link failed: Bad value
collect2: error: ld returned 1 exit status
Makefile:3641: recipe for target 'deftd' failed
make[2]: *** [deftd] Error 1

Can dev to fix this? Please.

this was brought to my attention shortly before ANN (https://github.com/deftchain/deft/issues/1).
newbie
Activity: 6
Merit: 0
Hm, have problem with compiling on ubuntu 16.04:

Code:
  CXXLD    deftd
/usr/bin/ld: libbitcoin_consensus.a(libbitcoin_consensus_a-balloon.o): relocation R_X86_64_PC32 against undefined symbol `SHA256_Init@@OPENSSL_1.0.0' can not be used when making a shared object; recompile with -fPIC
/usr/bin/ld: final link failed: Bad value
collect2: error: ld returned 1 exit status
Makefile:3641: recipe for target 'deftd' failed
make[2]: *** [deftd] Error 1

Can dev to fix this? Please.
newbie
Activity: 78
Merit: 0
member
Activity: 157
Merit: 10

Mission Statement Deft
A powerful high secured memory hard blockchain based on Stanford designed balloon hash will allow users to use the deft chain as a basic layer and deploy easily own parallel blockchains ( top-balloons) on the top of it and interoperate and collaborate between them, creating interconnected powerful secured blockchains (superclustered-balloons).  The Codebase of the deft chain will upgrade to the newest Version 0.16 and instead of one hashing method, we will introduce five variants of the revised balloon512 algo, which can be mined concurrently for fair user experience.

Introduction
The first cryptocurrency to implement the 'Balloon' memory-hard hashing function, superior in strength to Argon2, while remaining resistant to cache/side-channel attacks.
Additionally, the Balloon Hashing function does not require anywhere near as much memory to demonstrate its memory-hardness; making it possible for low-memory devices to verify hashes, an often overlooked but very important part of 'Proof of Work'.

What's a side-channel attack?
A term quickly referred to but rarely understood by most; a 'side-channel' attack refers to an attacker being able to use data obtained indirectly from the machine performing the hashing, to weaken or defeat the actual protection provided by the hashing in the first place.
Any hashing algorithm should not be susceptible to this; as i) multi-user operating system environments have become wide-spread since the 1980's and ii) we should expect the attacker to be able to be on the same system (albeit without the same level of privilege) and gain no advantage over the protection the hashing algorithm offers.

Argon2 vs Balloon
This is the most often quoted comparison; however, it is not safe/fair to compare the two algorithms, at least in a 'Proof of Work' paradigm.
Most algorithms, including all variations of Argon2 (Argon2d/i/id), converted in this sense pass the block header as the 'password' and the 'salt', to the hashing algorithm; which isn't quite the ideal usage scenario in the minds of the algorithm authors, however, it is safer than having a static 'salt'.
In a purely 'password hashing' arena; it should be noted several fairly serious attack methods have been identified and trialed against Argon2, some of these same attacks were still resistant against Balloon Hashing. Additionally, the password-hashing competition doesn't define cryptographic/hashing standards, it serves as a platform to bring the concept out in the open.
Argon2 is still a worthy candidate against Balloon, shoulder to shoulder. Unfortunately, some of the best discussion/debate is no longer available (http://gmane.org/details.php?group=gmane.comp.security.phc) due to abuse/being pulled offline.

Intriguing Benson, tell me more
The original password hashing algorithm was developed by Dan Boneh, Henry Corrigan-Gibbs and Stuart Schechter (https://crypto.stanford.edu/balloon/) and was submitted to the 'Password Hashing Competition' (https://password-hashing.net/).
The password hashing algorithm was later modified for PoW use last year and gradually refined since; the latest iteration being very small (2 files only requiring openssl lib/headers) and quite easy to implement; whilst remaining easy to introduce different length inputs, memory and mixing parameters.
Another version is currently being written/tested (identical parameters, so will be 100% compatible) that removes the current version's reliance on the openssl library; while not being expected to be any quicker, it will then become 100% platform-independent/portable.

deft specifications
PoW algorithm           Stanford balloon implementation (128kb per thread/4 mixing rounds of AES)
Coin ticker             DEFT
Coin codebase           Litecoin 0.15.1
Retarget code           Dual_KGW3 (with 3hr timeout)
Retarget strategy       Per block
Block time              4 minutes
Block maturity          30 blocks
Block subsidy           8.5 DEFT per block
Emission strategy       Starting off near zero, gradually increasing until 8.5 is reached by block 5000 (preventing instamining).
Emission decay          Block reward halves every 150,000 blocks
Emission simulation     Included in src folder as deftreward.c (gcc deftreward.c -o deftreward)
Coin marketcap          Maximum of 2.8 million DEFT (lifetime)
Coin premine            250,000 DEFT = 100.000 DEV, 75.000 Co-Founder, 75.000 DEFT set aside for bounties, marketing and competitions)


Reward Schedule
2                       0.0034 DEFT
1471                    2.5 DEFT
2941                    5. DEFT
5000                    8.5 DEFT
152500                  4.25 DEFT
302500                  2.125 DEFT
452500                  1.0625 DEFT
602500                  0.53125 DEFT
752500                  0.265625 DEFT
902500                  0.1328125 DEFT
1052500                 0.06640625 DEFT

Links/further reading
Github                  http://github.com/deftchain/deft
Win/MacWallet           https://github.com/deftchain/deft/releases
Miner                   https://github.com/deftchain/cpuminer-balloon
Pool module             https://github.com/deftchain/balloon_hash.git
Pool Statistics         https://deft.leafpool.com/
Discord                 https://discord.gg/M2RwYXB
Block Explorer          https://deft.ccore.online/
Website                     https://devsheaven.com/deft/
Balloon webpage         https://crypto.stanford.edu/balloon
Orig balloon code       https://github.com/henrycg/balloon
Balloon Whitepaper      https://eprint.iacr.org/2016/027.pdf
Twitter                 https://twitter.com/DeftChain
Telegram                https://t.me/deft_chain
Reddit                  https://www.reddit.com/r/DEFT

Exchanges
Crex24 - Disabled       https://crex24.com/exchange/DEFT-BTC
qtrade.io - Enabled     https://qtrade.io/market/DEFT_BTC

Pool: Leafpool
https://deft.leafpool.com/
cpuminer.exe -a balloon -o stratum+tcp://mine-deft.leafpool.com:6611 -u YOUR_DEFT_ADDRESS_HERE -p x -q


Translations, signature campaigns
Please note that while we will offer bounties/competitions in the future, we will not ask/request for translations, signature campaigns as we feel these sorts of thing (while well-intentioned) are tacky/cheap. If you'd like to translate in a language we don't support; feel free to submit and we will include it (for free).
We have several ideas in mind for interesting and unique bounties; so stay tuned
.

addnode=172.31.40.27
addnode=173.254.207.158
addnode=88.198.100.225
addnode=206.189.154.133
addnode=209.97.172.77




Pages:
Jump to: