Jump to content
  • Bitcoin Scrypt BTCS Information


    Smokeasy

    MANDATORY HARDFORK ON FEB 19 2018.  UPGRADE TO WALLET V.1.6.0

     

     

    BitcoinSLogo-512x512.png.3f8ee5007de470e21f1b12397a192c8d.png


     
    BITCOIN SCRYPT - BTCS
     
    Bitcoin sCrypt is the decentralized alternative to Bitcoin-core and is the first cryptographic currency to utilize CryptoVoter's decentralized blockchain voting to decide development issues and shift power away from developers and mining pools to coinholders themselves.

     

    CRYPTOCOINTALK FORUM LINKS

     

    GENERAL

     

    Main Announcement Thread:
    https://cryptocointalk.com/topic/1169-bitcoin-scrypt-btcs-information/

     

     

    DOWNLOADS
    All clients must upgrade to BTCS Wallet Client v.1.6.0 by February 19, 2018.

    Windows Wallet Installer

    Linux Wallet (coming soon)

    MAC Wallet (coming soon)

     

     

     

    SOURCE CODE

     

    BTCS Wallet Client v.1.6.0 Source Code:

    https://github.com/Bitcoin-sCrypt/Bitcoin-sCrypt

     

     

     

     

     

    EXTERNAL LINKS

     
    Websites

     

    http://bitcoinscrypt.io - Official Website

    http://theotherbitcoin.com - Developers' Blog
    http://bitcoinscrypt.org - Old Official Website (no longer updated)

     

     

    Block Explorers

     

    http://btcs.altcoinwarz.com:3005/

    http://coincave.nl:3603/

    http://blockchain-explorer.com

     

     

     

     

    SPECIFICATIONS

    • Scrypt Proof-of-Work Algorithm (100% POW)
    • Difficulty re-targets: nTargetTimespan = 60 * 60;  nTargetSpacing = 2 * 60; nInterval = nTargetTimespan / nTargetSpacing
    • 50 coins per block, 25 coins per block, Due to block halving now 12.5 coins per block.
    • 21 million total coins.

     

     

     

    Source Code
    https://github.com/Bitcoin-sCrypt/Bitcoin-Scrypt


     
     

    Sample bitcoin.conf

    rpcuser=username
    rpcpassword=password
    rpcallowip=localhost
    rpcport=30200
    addnode=45.55.216.92
    addnode=203.20.114.252
    addnode=192.81.216.69
    addnode=185.8.166.94
    addnode=195.181.208.162
    addnode=84.29.56.160
    addnode=104.131.186.185
    addnode=weminebtcs.com
    addnode=107.170.105.54
    addnode=104.131.157.75
    addnode=107.170.4.109
    addnode=31.193.130.77
    addnode=37.59.0.211
    addnode=54.201.183.106
    addnode=68.229.237.133
    
    server=1

     
    PORTS

    • P2P Port:  30201
    • RPC Port:  30200
    • Testnet Port:  30300

     

    POOLS
     

    CGMINER MINING POOL

    cgminer.exe --scrypt -o stratum+tcp://92.63.109.179:3333 -u YOUR_BTCS_ ADDRESS -p x

    http://coincave.nl 

     

    https://miningpower.net/

     

    https://pooldaddy.ws/

     

     

     

     

    EXCHANGES

     

    CRYPTOPIA

    http://cryptopia.co.nz

     

    C-CEX

    https://c-cex.com/?p=btcs-btc

     

     

    SOCIAL

     

    Facebook

    https://www.facebook.com/theotherbitcoin

    You Tube
    https://www.youtube.com/user/bitcoinscrypt

     

     

    Twitter
     

    https://twitter.com/theotherbitcoin

     

     

    SERVICES / OTHER

     

    Coin Cap

    http://coincap.io/

     

    Coin Market Cap

    http://coinmarketcap.com/

     

    Coin Market Info

    http://crypto-prices.com/

     
     

    Mining Calculator

    https://cointweak.com/calculator/coin/btcs

     

     

     

     

    • Winner 1


    User Feedback

    Recommended Comments



    I've completed the fix and tested and everything is good to go.  Just need to have CaptChadd merge with older version and compile the executable.  I fixed the problems with the gitian yml files so now everybody can compile deterministic builds themselves with gitian and compare the files' checksum hashes instead of simply relying on a developer's pre-compiled binaries so that we can move away from centralized trust to decentralized trust.

     

    I'll provide more info tomorrow but I made the following changes to client (v.1.2.0):

    1. Fixed the issue with the initial blockchain download allowing for complete download of the blockchain from scratch.
    2. Added CaptChadd's node (31.193.130.77) to the source as a seed node allowing for much better connects without editing the conf file or using --addnode.
    3. Added checkpoints at the 0, 11111, 33333, 55555 and 60000 block heights to create static checkpoints and better secure the blockchain.
    4. Enabled the QR generator so now the client can generate QR codes.
    5. Enabled the Windows Installer and the daemon.
    6. Fixed the yml files in ../contrib/gitian-descriptors so the gitian builds work like a charm
    7. Created step-by-step directions on creating a gitian build for windows so that anyone can compile the windows client from the source-code and compare their files' checksum hashes with other user's.
    8. Changed the logo to reflect Bitcoin sCrypt instead of Bitcoin 2.

     

    I do not plan on distributing any Windows binaries, under the assumption that CaptChadd will compile and distribute the binaries through the bitcoinscrypt.org website, but I will provide the checksum hashes of my gitian builds of the Windows client so you can compare binaries you compile yourself or get from CaptChadd.  I'm going to talk to CaptChadd about adding gitian.sigs to Omega's github site so that anyone can build the Windows client from source and post their compiled binary files' checksum hashes because users of cryptographic currencies need to get away from trusting pre-compiled binaries from a single centralized source.

     

    Speaking of which, the source-code of the revised client (v.1.2.0) will be provided tomorrow after some much need sleep.  Hopefully, the compiled Windows binaries will be released shortly thereafter.

     

    Regards,

     

    Smokeasy

     

    This is stunning work and we are right now in the process of merging this updated code to the repo and I will indeed compile a Windows Client to put on the website and on here.

     

    Its exciting times for this coin.

    Share this comment


    Link to comment
    Share on other sites

    I have just noticed that the link for the block explorer is down. Does anyone have any spare time to host a block explorer for this coin please?

    Share this comment


    Link to comment
    Share on other sites

    OK, was having problems with pulling Smokeasy's updates, so I merged it to Omega's repo manually which is now complete. The Version 1.2.0 source code is now live on the Github Repo.

     

    I will be compiling a Windows client for this update either night or tomorrow, which I will post a link to on here and the website.

     

    Cheers.

    Share this comment


    Link to comment
    Share on other sites

    OK, was having problems with pulling Smokeasy's updates, so I merged it to Omega's repo manually which is now complete. The Version 1.2.0 source code is now live on the Github Repo.

     

    I will be compiling a Windows client for this update either night or tomorrow, which I will post a link to on here and the website.

     

    Cheers.

     

    Sounds great!  People are going to be happy about this.   :)

    Share this comment


    Link to comment
    Share on other sites

    This is great thank you. Watching this like a hawk! This is going to be interesting

    Share this comment


    Link to comment
    Share on other sites

    Please do not use the link that was above, that client was compiled with some invalid code due to Github. Also the source code is getting updated too, so please don't compile from it just yet.

     

    Thanks

    Share this comment


    Link to comment
    Share on other sites

    hi i do not know about mining willi be able to mine like i did with simply my laptop

    Share this comment


    Link to comment
    Share on other sites

    http://blocks.btc2.pw

     

    Block explorer is back online.  I was waiting for the updated client, because the previous one was crashing which would require manually restarting the block explorer very frequently.  Glad to see the update!

     

    Thanks Novebitme!

    Share this comment


    Link to comment
    Share on other sites

    The wallet, will it still interfere with the BTC SHA 256 wallet? We might have much wider adoption if the Users\blablabla\AppData\Roaming\Bitcoin folder is changed to AppData\Roaming\BitcoinScrypt or BitcoinS or something, as I understand it the two wallets would them be able to exist side by side? On that note, is the v.1.2 version on the front page of this thread the correct wallet and it syncs from the start?

     

    Thanks guys. I see a lot of new kHash on this already, diff rising :) Good news for adoption...

    Share this comment


    Link to comment
    Share on other sites

    The wallet, will it still interfere with the BTC SHA 256 wallet? We might have much wider adoption if the Users\blablabla\AppData\Roaming\Bitcoin folder is changed to AppData\Roaming\BitcoinScrypt or BitcoinS or something, as I understand it the two wallets would them be able to exist side by side? On that note, is the v.1.2 version on the front page of this thread the correct wallet and it syncs from the start?

     

    Thanks guys. I see a lot of new kHash on this already, diff rising :) Good news for adoption...

     

    The new version (v.1.2.0) uses a different AppData folder and no longer interferes with the Bitcoin SHA256 client.  This change should lead to wider adoption.  The new AppData folder is /Bitcoin-sCrypt so you may need to transfer your wallet.dat file (always back-up your wallet.dat file before touching it).

     

    Also, the new version of the Windows client (v.1.2.0) is now available on the front page of this thread as you suggested.

    Share this comment


    Link to comment
    Share on other sites

    I just tested. You would have to included a bitcoin.conf file to get it connect to the network nod. otherwise, it would not connect.

     

    rpcuser=username
    rpcpassword=password
    rpcallowip=localhost
    rpcport=30200
    addnode=31.193.130.77
    server=1
    gen=0

    Share this comment


    Link to comment
    Share on other sites

    I just tested. You would have to included a bitcoin.conf file to get it connect to the network nod. otherwise, it would not connect.

     

    rpcuser=username

    rpcpassword=password

    rpcallowip=localhost

    rpcport=30200

    addnode=31.193.130.77

    server=1

    gen=0

     

    Sometimes simply restarting the client (without changing the conf file) works.  Kind of odd but shouldn't have any connection problems once it initially connects.

    Share this comment


    Link to comment
    Share on other sites
    frottirzokni

    Posted

    <p>why is the total network hashrate oscillate violently between 3 to 200 MH/s in a matter of a minute? is it a computing mistake?</p>

    Share this comment


    Link to comment
    Share on other sites



    Create an account or sign in to comment

    You need to be a member in order to leave a comment

    Create an account

    Sign up for a new account in our community. It's easy!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now

Cryptocurrenytalk Logo

 

News, information, and discussions about cryptocurrencies, blockchains, technology, and events. Blockchaintalk is your source for advice on what to mine, technical details, new launch announcements, and advice from trusted members of the community. Cryptocurrencytalk is your source for everything crypto. We love discussing the world of cryptocurrencies.

 

   
×
×
  • Create New...

Important Information

By using CRYPTOCURRENCYTALK.COM, you agree to our Terms of Use.