Bitcoin Forum
March 29, 2024, 10:32:49 AM *
News: Latest Bitcoin Core release: 26.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1] 2 3 4 5 6 7 »  All
  Print  
Author Topic: [ANN][POW] BSHA3: SHA3d unleashed  (Read 20642 times)
ch4ot1c (OP)
Newbie
*
Offline Offline

Activity: 10
Merit: 0


View Profile
October 31, 2018, 06:11:25 PM
Last edit: November 21, 2018, 06:01:59 PM by ch4ot1c
 #1

On October 31, 2008, Satoshi Nakamoto sent his first email discussing Bitcoin. Ever since then, the world has felt the full impact of SHA256. We have neglected its wise cousin though, SHA3-256, in the discussion of Proof of Work algorithms. Ten years later, it is finally time.

Most instances of SHA256 have been replaced with SHA3 in the Bitcoin codebase, to form this new protocol. This includes cases that use HMACs and HASH160. Additionally, SHA1 has been removed.

Source Code: https://github.com/bsha3/bsha3
Latest Version: https://github.com/bsha3/bsha3/releases
Block Explorer: http://explorer.bsha3.com, Community: https://chainmapper.com/bsha3

Website: https://bsha3.com, also https://bsha3.org
Twitter: @bsha3official
Discord: https://discord.gg/tjzc3AZ
QQ (China): 755722635

I created BSHA3 because SHA3d's impact has yet to be seen in on the internet and world community. I wonder the solution to this hard consensus problem: Is SHA256d or SHA3d driven proof-of-work more efficient?

The roadmap is to stay consistent with Bitcoin Core code. They have done an outstanding job of conquering nuances and bugs in Bitcoin, including transaction malleability, and we are in a position to simply continue porting their improvements.

**Please note that this project is simply an experimental blockchain mainnet.**

Proof of Work

SHA3d. This is the first blockchain to use this algorithm! It is like SHA3-256, but two iterations each time - in the spirit of Bitcoin's SHA256d. Nerd note: It uses the Keccak-1600 with the 0x01 -> 0x06 last-minute padding fix (Ethereum forgot to do this! Sad).

In addition, there is an easy to use CPU miner integrated into the daemon itself! Just run
Code:
setgenerate true <num_cores>
to begin, and
Code:
setgenerate false
to stop.

A GPU miner has also been developed by a community member - check the Github!

Premine?

BSHA3 is "premined" only up to block 250. This allowed for testing above block 101 + 16, as well as a brief network-preparation / stats-gathering period before release. Its public announcement is today, October 31, 2018, during the 50 "coin" block-reward period.

Coin generation

Miners begin generating 50 coins per block, with 10 minute average blocks. The same exact issuance schedule & difficulty adjustment as Bitcoin is used! Only 21,000,000 BSHA3 are ever created.

Source code

The source code is here:
https://github.com/bsha3/bsha3

Please read the front page (README.md) for instructions on building, running, and mining.

Community coin

I, Jon Layton, am the inventor of BSHA3. After this announcement though, nothing about the protocol and its function belongs to me.

All of the source code is Free Software (unless otherwise licensed), and contributing works are referenced in the COPYING file.

In this spirit, the community must band together to build important ecosystem features - wallets, explorers, and more. This announcement can serve as an initial hub for planning and discussion.

If you live in the state of New York, I respectfully ask you to not participate in this project in any way.

Running

The BSHA3 implementation is based on the latest Bitcoin code. You can build the daemon version (bsha3d with bsha3-cli) and/or the gui version (bsha3-qt). See the docs on Github for more information.

Similar to Bitcoin, you may want to create a bitcoin.conf file here:
  Win10: C:\Documents and Settings\<username>\Application Data\BSHA3
  Win7: C:\Users\<username>\AppData\Roaming\BSHA3
  Mac: ~/Library/Application Support/BSHA3
  Unix: ~/.bsha3

P2P Port: 8335
Open this port on your router to allow more than 8 connections.

RPC Port: 8334
This is the port miners will use to communicate with your client/daemon. In general, do not expose this one to the public network.

Sample ~/.bsha3/bitcoin.conf file (optional):

Code:
server=1

#Change this if you want to use a different rpc port for mining
#rpcport=8334

#Uncomment this if you are running bsha3d and want it to run in the background
#daemon=1

#addnode=<ip of trusted peer 1>
#addnode=<ip of trusted peer 2>


Gitian releases and more coming soon! Stay tuned here for updates.

Mine away!
1711708369
Hero Member
*
Offline Offline

Posts: 1711708369

View Profile Personal Message (Offline)

Ignore
1711708369
Reply with quote  #2

1711708369
Report to moderator
1711708369
Hero Member
*
Offline Offline

Posts: 1711708369

View Profile Personal Message (Offline)

Ignore
1711708369
Reply with quote  #2

1711708369
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1711708369
Hero Member
*
Offline Offline

Posts: 1711708369

View Profile Personal Message (Offline)

Ignore
1711708369
Reply with quote  #2

1711708369
Report to moderator
RogerFun
Newbie
*
Offline Offline

Activity: 85
Merit: 0


View Profile
October 31, 2018, 06:45:58 PM
 #2

how to build or links to binaries?
busminer
Hero Member
*****
Offline Offline

Activity: 1764
Merit: 570


Twitter\X @AlexKosa1


View Profile WWW
October 31, 2018, 06:57:33 PM
 #3

any windows wallet?

j4rd4
Newbie
*
Offline Offline

Activity: 41
Merit: 0


View Profile
October 31, 2018, 07:00:16 PM
 #4

tried to compile, ended with an error:
  CXX      test/test_bitcoin-test_bitcoin.o
test/test_bitcoin.cpp: In constructor ‘BasicTestingSetup::BasicTestingSetup(const string&)’:
test/test_bitcoin.cpp:64:70: error: ‘NO_TIMEOUT’ is not a member of ‘Consensus::BIP9Deployment’
     gArgs.ForceSetArg("-vbparams", strprintf("segwit:0:%d", (int64_t)Consensus::BIP9Deployment::NO_TIMEOUT));
makoky
Newbie
*
Offline Offline

Activity: 14
Merit: 1


View Profile
October 31, 2018, 07:05:19 PM
 #5

the same error for me
ch4ot1c (OP)
Newbie
*
Offline Offline

Activity: 10
Merit: 0


View Profile
October 31, 2018, 07:13:27 PM
 #6

That error is after
Code:
bsha3d
and
Code:
bsha3-cli
are finished building; you can still use the program. I'll get to the tests shortly!
RogerFun
Newbie
*
Offline Offline

Activity: 85
Merit: 0


View Profile
October 31, 2018, 08:12:09 PM
 #7

ok i managed to compile and i also got the same errors. but also i dont see how i can run the daemon ?
makoky
Newbie
*
Offline Offline

Activity: 14
Merit: 1


View Profile
October 31, 2018, 08:12:29 PM
 #8

why the miner its called ravenminer?
RogerFun
Newbie
*
Offline Offline

Activity: 85
Merit: 0


View Profile
October 31, 2018, 09:41:14 PM
 #9

is this actually mining ravencoin  Undecided Undecided Undecided Undecided Undecided Undecided
samspaces
Legendary
*
Offline Offline

Activity: 1451
Merit: 1030


View Profile
October 31, 2018, 10:01:58 PM
 #10

daemon and cli aren't built in src/ after following error.

  CXX      qt/test/qt_test_test_bsha3_qt-addressbooktests.o
test/test_bitcoin.cpp: In constructor ‘BasicTestingSetup::BasicTestingSetup(const string&)’:
test/test_bitcoin.cpp:64:70: error: ‘NO_TIMEOUT’ is not a member of ‘Consensus::BIP9Deployment’
     gArgs.ForceSetArg("-vbparams", strprintf("segwit:0:%d", (int64_t)Consensus::BIP9Deployment::NO_TIMEOUT));
                                                                      ^
Makefile:9127: recipe for target 'test/qt_test_test_bsha3_qt-test_bitcoin.o' failed
make[2]: *** [test/qt_test_test_bsha3_qt-test_bitcoin.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory '/home/wallets/bsha3/src'
Makefile:10492: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/wallets/bsha3/src'
Makefile:774: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1
dquancey
Hero Member
*****
Offline Offline

Activity: 587
Merit: 500


View Profile
October 31, 2018, 10:23:21 PM
 #11

Anyone have a balance at all?
RogerFun
Newbie
*
Offline Offline

Activity: 85
Merit: 0


View Profile
October 31, 2018, 10:30:12 PM
 #12

nopes. not sure what's going on and hash is climbing. but no coins.
CryptoJayC
Jr. Member
*
Offline Offline

Activity: 71
Merit: 1


View Profile
October 31, 2018, 10:36:17 PM
 #13

consensus.nMinerConfirmationWindow = 2016

I believe it takes 2016 blocks to confirm a mined block.
RogerFun
Newbie
*
Offline Offline

Activity: 85
Merit: 0


View Profile
October 31, 2018, 10:41:21 PM
 #14

yeah i was thinking the same. but help me out here - is there a way to see unconfirmed blocks through the console?
CryptoJayC
Jr. Member
*
Offline Offline

Activity: 71
Merit: 1


View Profile
October 31, 2018, 10:42:29 PM
 #15

./bsha3-cli listtransactions
CryptoJayC
Jr. Member
*
Offline Offline

Activity: 71
Merit: 1


View Profile
October 31, 2018, 10:46:32 PM
 #16

Lol, 2016 blocks at 10 minute block times? You realize that is a 2 week confirmation period right..

isn't it the same for bitcoin?

i agree it's a very long time for confirmation.
RogerFun
Newbie
*
Offline Offline

Activity: 85
Merit: 0


View Profile
October 31, 2018, 10:47:33 PM
 #17

oh shit. this i didnt realize. ok that's an amazing non starter
boba022
Jr. Member
*
Offline Offline

Activity: 44
Merit: 1


View Profile
November 01, 2018, 02:40:23 AM
 #18

Any plans to promote the coin? Or it'll be completely up to community to work on increasing adoption?
RogerFun
Newbie
*
Offline Offline

Activity: 85
Merit: 0


View Profile
November 01, 2018, 03:58:46 AM
 #19

net hash went 4x since 3 hrs and all without even any binary files. i see dev working on github ferociously. promotion can wait given all of these.
CryptoJayC
Jr. Member
*
Offline Offline

Activity: 71
Merit: 1


View Profile
November 01, 2018, 04:06:38 AM
 #20

Lol, 2016 blocks at 10 minute block times? You realize that is a 2 week confirmation period right..

isn't it the same for bitcoin?

i agree it's a very long time for confirmation.

It is, same as all other forks too (RVN, Sys, etc.) The difference is that their block times are different.
I was wrong then.
mined block has confirmed after 101 blocks.
That 2016 is not the line of code that suggests number of confirmations needed for mined block.
Pages: [1] 2 3 4 5 6 7 »  All
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!