Topic: [ANN][POW] BSHA3: SHA3d unleashed - page 7. (Read 20685 times)

./bsha3-cli listtransactions

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

consensus.nMinerConfirmationWindow = 2016

I believe it takes 2016 blocks to confirm a mined block.

nopes. not sure what's going on and hash is climbing. but no coins.

No windows?

Anyone have a balance at all?

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

is this actually mining ravencoin 

why the miner its called ravenminer?

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

That error is after and are finished building; you can still use the program. I'll get to the tests shortly!

the same error for me

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));

any windows wallet?

how to build or links to binaries?

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! ).

In addition, there is an easy to use CPU miner integrated into the daemon itself! Just run to begin, and 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\\Application Data\BSHA3
  Win7: C:\Users\\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=
#addnode=

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

Mine away!