Bitcoin Full Nodes: What They Are and How to Set One Up ...

Fun with low fee TXNs on Mainnet

Here's a 0.493 sat/vB TXN I put on mainnet today. You'll have to use the SoChain block explorer to see it though. I give it a 3% chance of getting confirmed, but we'll wait and see. The TXN is a donation to [email protected] since I use their seeder for my network herder.
So last month, I voiced the unpopular opinion that node operators should lower the minrelaytxfee setting to allow low-fee TXNs to propagate more freely throughout the network. Then I asked why miners weren't mining 0.999 sat/vB TXNs during idle periods since it should be more profitable than mining no TXNs at all. Finally I wrote a node herder to walk the network looking for node operators that were running minrelaytxfee below the default (1000 sat). After walking about 26% of the network, turns out about 5% of nodes are allowing low fee TXNs.
So in that vein of discussion, I decided to just sign some low-fee TXNs and send them to the 5% of nodes I found and see what happens. To my surprise it showed up on one of the 23 block explorers I tried after broadcasting it. Surprisingly, that comes out to about 5% of explorers accepting low fee TXNs as well. So hopefully 5% or so of the miners will confirm low fee TXNs. We'll see.
BTW, to do this, this is what I did.
  1. Pair my HW wallet to Electrum
  2. Use the paytomany Electrum API to craft a TXN below 1 sat/vB
  3. Import the TXN to sign in Electrum
  4. Ran a full node with minrelaytxfee set to 1 sat (0.001 sat/vB)
  5. Walked the network to find a good number of low-fee peers
  6. Use bitcoin addnode API to herd my node to the low-fee peers I discovered.
  7. Use bitcoin sendrawtransaction API to broadcast TXN
Wait and see if it can propagate to a miner and if a miner will accept it.
BTW, there is a PR to lower the minrelaytxfee in core, but it's dragged on for years. The setting was lowered about every year or so in the early days, but hasn't been touched for many years now.
submitted by brianddk to Bitcoin [link] [comments]

Does -addnode create an outbound connection? /r/Bitcoin

Does -addnode create an outbound connection? /Bitcoin submitted by ABitcoinAllBot to BitcoinAll [link] [comments]

How to run two bitcoind processes in isolation (Windows)

I have a synced node, and I would like to create a pruned copy of that node without destroying all blocks and chainstate I already have. My thought would be to run two copies of bitcoin {BitcoinA.exe, BitcoinB.exe}, while offline and bound to 127.0.0.1. Both A and B point to each other through a connect or addnode config setting. My thought would be that now the "blank" bitcoin node (BitcoinB) would download and prune all the block data from BitcoinA via localhost.
I can imagine that I'd need separate data, block and chainstate dirs. I'll need separate rpc-cookies and separate ports.
Obviously I could just do the 300 GB file copy then do a rescan, but I figured I'd get faster IO on localhost<->localhost than disk<->disk.
Surely this is a fairly common way to clone block data. Has anyone done this before? Thoughts or advice?
submitted by brianddk to Bitcoin [link] [comments]

A simple game of node tag to increase your incoming connection count.

Become one of the 1% of "listening" (aka "super") nodes.
Recently played with setting up an onion node and found for the first day or so it was difficult to get incoming connections via tor. If anyone wants to increase their incoming connection count, just DM me your network and node info and I'll addnode you. If you don't care about association, you can just reply with your node info on thread.
```

Format

:

Examples

mainnet 88.99.167.175:8333 mainnet [2a01:4f8:10a:37ee::2]:8333 mainnet pymhrtleulgjtjpv.onion:8333 testnet 88.99.167.175:18333 ```
If you want to do the same, just ask for node info on this thread or ask for DMs as well. To add named nodes at startup, add the following to your bitcoin.conf. These are just random public nodes, obviously add your own nodes in your conf file.
```

Mainnet nodes in the 'main' section

[main]

https://bitnodes.io/

addnode=88.99.167.175:8333 addnode=[2a01:4f8:10a:37ee::2]:8333

random node

pymhrtleulgjtjpv.onion:8333

Testnet nodes in the 'test' section

[test]

https://bitnodes.io/

addnode=88.99.167.175:18333

random node

addnode=3v6wv6ibu4r6hn6p.onion:18333 ```
* - Reserve the right to filter based on reddit karma
submitted by brianddk to Bitcoin [link] [comments]

[ANN][ANDROID MINING][AIRDROP] NewEnglandcoin: Scrypt RandomSpike

New England
New England 6 States Songs: https://www.reddit.com/newengland/comments/er8wxd/new_england_6_states_songs/
NewEnglandcoin
Symbol: NENG
NewEnglandcoin is a clone of Bitcoin using scrypt as a proof-of-work algorithm with enhanced features to protect against 51% attack and decentralize on mining to allow diversified mining rigs across CPUs, GPUs, ASICs and Android phones.
Mining Algorithm: Scrypt with RandomSpike. RandomSpike is 3rd generation of Dynamic Difficulty (DynDiff) algorithm on top of scrypt.
1 minute block targets base difficulty reset: every 1440 blocks subsidy halves in 2.1m blocks (~ 2 to 4 years) 84,000,000,000 total maximum NENG 20000 NENG per block Pre-mine: 1% - reserved for dev fund ICO: None RPCPort: 6376 Port: 6377
NewEnglandcoin has dogecoin like supply at 84 billion maximum NENG. This huge supply insures that NENG is suitable for retail transactions and daily use. The inflation schedule of NengEnglandcoin is actually identical to that of Litecoin. Bitcoin and Litecoin are already proven to be great long term store of value. The Litecoin-like NENG inflation schedule will make NewEnglandcoin ideal for long term investment appreciation as the supply is limited and capped at a fixed number
Bitcoin Fork - Suitable for Home Hobbyists
NewEnglandcoin core wallet continues to maintain version tag of "Satoshi v0.8.7.5" because NewEnglandcoin is very much an exact clone of bitcoin plus some mining feature changes with DynDiff algorithm. NewEnglandcoin is very suitable as lite version of bitcoin for educational purpose on desktop mining, full node running and bitcoin programming using bitcoin-json APIs.
The NewEnglandcoin (NENG) mining algorithm original upgrade ideas were mainly designed for decentralization of mining rigs on scrypt, which is same algo as litecoin/dogecoin. The way it is going now is that NENG is very suitable for bitcoin/litecoin/dogecoin hobbyists who can not , will not spend huge money to run noisy ASIC/GPU mining equipments, but still want to mine NENG at home with quiet simple CPU/GPU or with a cheap ASIC like FutureBit Moonlander 2 USB or Apollo pod on solo mining setup to obtain very decent profitable results. NENG allows bitcoin litecoin hobbyists to experience full node running, solo mining, CPU/GPU/ASIC for a fun experience at home at cheap cost without breaking bank on equipment or electricity.
MIT Free Course - 23 lectures about Bitcoin, Blockchain and Finance (Fall,2018)
https://www.youtube.com/playlist?list=PLUl4u3cNGP63UUkfL0onkxF6MYgVa04Fn
CPU Minable Coin Because of dynamic difficulty algorithm on top of scrypt, NewEnglandcoin is CPU Minable. Users can easily set up full node for mining at Home PC or Mac using our dedicated cheetah software.
Research on the first forked 50 blocks on v1.2.0 core confirmed that ASIC/GPU miners mined 66% of 50 blocks, CPU miners mined the remaining 34%.
NENG v1.4.0 release enabled CPU mining inside android phones.
Youtube Video Tutorial
How to CPU Mine NewEnglandcoin (NENG) in Windows 10 Part 1 https://www.youtube.com/watch?v=sdOoPvAjzlE How to CPU Mine NewEnglandcoin (NENG) in Windows 10 Part 2 https://www.youtube.com/watch?v=nHnRJvJRzZg
How to CPU Mine NewEnglandcoin (NENG) in macOS https://www.youtube.com/watch?v=Zj7NLMeNSOQ
Decentralization and Community Driven NewEnglandcoin is a decentralized coin just like bitcoin. There is no boss on NewEnglandcoin. Nobody nor the dev owns NENG.
We know a coin is worth nothing if there is no backing from community. Therefore, we as dev do not intend to make decision on this coin solely by ourselves. It is our expectation that NewEnglandcoin community will make majority of decisions on direction of this coin from now on. We as dev merely view our-self as coin creater and technical support of this coin while providing NENG a permanent home at ShorelineCrypto Exchange.
Twitter Airdrop
Follow NENG twitter and receive 100,000 NENG on Twitter Airdrop to up to 1000 winners
Graphic Redesign Bounty
Top one award: 90.9 million NENG Top 10 Winners: 500,000 NENG / person Event Timing: March 25, 2019 - Present Event Address: NewEnglandcoin DISCORD at: https://discord.gg/UPeBwgs
Please complete above Twitter Bounty requirement first. Then follow Below Steps to qualify for the Bounty: (1) Required: submit your own designed NENG logo picture in gif, png jpg or any other common graphic file format into DISCORD "bounty-submission" board (2) Optional: submit a second graphic for logo or any other marketing purposes into "bounty-submission" board. (3) Complete below form.
Please limit your submission to no more than two total. Delete any wrongly submitted or undesired graphics in the board. Contact DISCORD u/honglu69#5911 or u/krypton#6139 if you have any issues.
Twitter Airdrop/Graphic Redesign bounty sign up: https://goo.gl/forms/L0vcwmVi8c76cR7m1
Milestones
Roadmap
NENG v1.4.0 Android Mining, randomSpike Evaluation https://github.com/ShorelineCrypto/NewEnglandCoin/releases/download/NENG_2020_Q3_report/NENG_2020_Q3_report.pdf
RandomSpike - NENG core v1.3.0 Hardfork Upgrade Proposal https://github.com/ShorelineCrypto/NewEnglandCoin/releases/download/2020Q1_Report/Scrypt_RandomSpike_NENGv1.3.0_Hardfork_Proposal.pdf
NENG Security, Decentralization & Valuation
https://github.com/ShorelineCrypto/NewEnglandCoin/releases/download/2019Q2_report/NENG_Security_Decentralization_Value.pdf
Whitepaper v1.0 https://github.com/ShorelineCrypto/NewEnglandCoin/releases/download/whitepaper_v1.0/NENG_WhitePaper.pdf
DISCORD https://discord.gg/UPeBwgs
Explorer
http://www.findblocks.com/exploreNENG http://86.100.49.209/exploreNENG http://nengexplorer.mooo.com:3001/
Step by step guide on how to setup an explorer: https://github.com/ShorelineCrypto/nengexplorer
Github https://github.com/ShorelineCrypto/NewEnglandCoin
Wallet
Android with UserLand App (arm64/armhf), Chromebook (x64/arm64/armhf): https://github.com/ShorelineCrypto/NewEnglandCoin/releases/tag/v1.4.0.5
Linux Wallet (Ubuntu/Linux Mint, Debian/MX Linux, Arch/Manjaro, Fedora, openSUSE): https://github.com/ShorelineCrypto/NewEnglandCoin/releases/tag/v1.4.0.3
MacOS Wallet (10.11 El Capitan or higher): https://github.com/ShorelineCrypto/NewEnglandCoin/releases/tag/v1.4.0.2
Android with GNUroot on 32 bits old Phones (alpha release) wallet: https://github.com/ShorelineCrypto/NewEnglandCoin/releases/tag/v1.4.0
Windows wallet: https://github.com/ShorelineCrypto/NewEnglandCoin/releases/tag/v1.3.0.1
addnode ip address for the wallet to sync faster, frequently updated conf file: https://github.com/ShorelineCrypto/cheetah_cpumineblob/mastenewenglandcoin.conf-example
How to Sync Full Node Desktop Wallet https://www.reddit.com/NewEnglandCoin/comments/er6f0q/how_to_sync_full_node_desktop_wallet/
TWITTER https://twitter.com/newenglandcoin
REDDIT https://www.reddit.com/NewEnglandCoin/
Cheetah CPU Miner Software https://github.com/ShorelineCrypto/cheetah_cpuminer
Solo Mining with GPU or ASIC https://bitcointalk.org/index.php?topic=5027091.msg52187727#msg52187727
How to Run Two Full Node in Same Desktop PC https://bitcointalk.org/index.php?topic=5027091.msg53581449#msg53581449
ASIC/GPU Mining Pools Warning to Big ASIC Miners Due to DynDiff Algo on top of Scrypt, solo mining is recommended for ASIC/GPU miners. Further more, even for mining pools, small mining pool will generate better performance than big NENG mining pool because of new algo v1.2.x post hard fork.
The set up configuration of NENG for scrypt pool mining is same as a typical normal scrypt coin. In other word, DynDiff on Scrypt algo is backward compatible with Scrypt algo. Because ASIC/GPU miners rely on CPU miners for smooth blockchain movement, checkout bottom of "Latest News" section for A WARNING to All ASIC miners before you decide to dump big ASIC hash rate into NENG mining.
(1) Original DynDiff Warning: https://bitcointalk.org/index.php?topic=5027091.msg48324708#msg48324708 (2) New Warning on RandomSpike Spike difficulty (244k) introduced in RandomSpike served as roadblocks to instant mining and provide security against 51% attack risk. However, this spike difficulty like a roadblock that makes big ASIC mining less profitable. In case of spike block to be mined, the spike difficulty immediately serve as base difficulty, which will block GPU/ASIC miners effectively and leave CPU cheetah solo miners dominating mining almost 100% until next base difficulty reset.
FindBlocks http://findblocks.com/
CRpool http://crpool.xyz/
Cminors' Pool http://newenglandcoin.cminors-pool.com/
SPOOL https://spools.online/
Exchange
📷
https://shorelinecrypto.com/
Features: anonymous sign up and trading. No restriction or limit on deposit or withdraw.
The trading pairs available: NewEnglandcoin (NENG) / Dogecoin (DOGE)
Trading commission: A round trip trading will incur 0.10% trading fees in average. Fees are paid only on buyer side. buy fee: 0.2% / sell fee: 0% Deposit fees: free for all coins Withdraw fees: ZERO per withdraw. Mining fees are appointed by each coin blockchain. To cover the blockchain mining fees, there is minimum balance per coin per account: * Dogecoin 2 DOGE * NewEnglandcoin 1 NENG
Latest News Aug 30, 2020 - NENG v1.4.0.5 Released for Android/Chromebook Upgrade with armhf, better hardware support https://bitcointalk.org/index.php?topic=5027091.msg55098029#msg55098029
Aug 11, 2020 - NENG v1.4.0.4 Released for Android arm64 Upgrade / Chromebook Support https://bitcointalk.org/index.php?topic=5027091.msg54977437#msg54977437
Jul 30, 2020 - NENG v1.4.0.3 Released for Linux Wallet Upgrade with 8 Distros https://bitcointalk.org/index.php?topic=5027091.msg54898540#msg54898540
Jul 21, 2020 - NENG v1.4.0.2 Released for MacOS Upgrade with Catalina https://bitcointalk.org/index.php?topic=5027091.msg54839522#msg54839522
Jul 19, 2020 - NENG v1.4.0.1 Released for MacOS Wallet Upgrade https://bitcointalk.org/index.php?topic=5027091.msg54830333#msg54830333
Jul 15, 2020 - NENG v1.4.0 Released for Android Mining, Ubuntu 20.04 support https://bitcointalk.org/index.php?topic=5027091.msg54803639#msg54803639
Jul 11, 2020 - NENG v1.4.0 Android Mining, randomSpike Evaluation https://bitcointalk.org/index.php?topic=5027091.msg54777222#msg54777222
Jun 27, 2020 - Pre-Announce: NENG v1.4.0 Proposal for Mobile Miner Upgrade, Android Mining Start in July 2020 https://bitcointalk.org/index.php?topic=5027091.msg54694233#msg54694233
Jun 19, 2020 - Best Practice for Futurebit Moonlander2 USB ASIC on solo mining mode https://bitcointalk.org/index.php?topic=5027091.msg54645726#msg54645726
Mar 15, 2020 - Scrypt RandomSpike - NENG v1.3.0.1 Released for better wallet syncing https://bitcointalk.org/index.php?topic=5027091.msg54030923#msg54030923
Feb 23, 2020 - Scrypt RandomSpike - NENG Core v1.3.0 Relased, Hardfork on Mar 1 https://bitcointalk.org/index.php?topic=5027091.msg53900926#msg53900926
Feb 1, 2020 - Scrypt RandomSpike Proposal Published- NENG 1.3.0 Hardfork https://bitcointalk.org/index.php?topic=5027091.msg53735458#msg53735458
Jan 15, 2020 - NewEnglandcoin Dev Team Expanded with New Kickoff https://bitcointalk.org/index.php?topic=5027091.msg53617358#msg53617358
Jan 12, 2020 - Explanation of Base Diff Reset and Effect of Supply https://www.reddit.com/NewEnglandCoin/comments/envmo1/explanation_of_base_diff_reset_and_effect_of/
Dec 19, 2019 - Shoreline_tradingbot version 1.0 is released https://bitcointalk.org/index.php?topic=5121953.msg53391184#msg53391184
Sept 1, 2019 - NewEnglandcoin (NENG) is Selected as Shoreline Tradingbot First Supported Coin https://bitcointalk.org/index.php?topic=5027091.msg52331201#msg52331201
Aug 15, 2019 - Mining Update on Effect of Base Difficulty Reset, GPU vs ASIC https://bitcointalk.org/index.php?topic=5027091.msg52169572#msg52169572
Jul 7, 2019 - CPU Mining on macOS Mojave is supported under latest Cheetah_Cpuminer Release https://bitcointalk.org/index.php?topic=5027091.msg51745839#msg51745839
Jun 1, 2019 - NENG Fiat project is stopped by Square, Inc https://bitcointalk.org/index.php?topic=5027091.msg51312291#msg51312291
Apr 21, 2019 - NENG Fiat Project is Launched by ShorelineCrypto https://bitcointalk.org/index.php?topic=5027091.msg50714764#msg50714764
Apr 7, 2019 - Announcement of Fiat Project for all U.S. Residents & Mobile Miner Project Initiation https://bitcointalk.org/index.php?topic=5027091.msg50506585#msg50506585
Apr 1, 2019 - Disclosure on Large Buying on NENG at ShorelineCrypto Exchange https://bitcointalk.org/index.php?topic=5027091.msg50417196#msg50417196
Mar 27, 2019 - Disclosure on Large Buying on NENG at ShorelineCrypto Exchange https://bitcointalk.org/index.php?topic=5027091.msg50332097#msg50332097
Mar 17, 2019 - Disclosure on Large Buying on NENG at ShorelineCrypto Exchange https://bitcointalk.org/index.php?topic=5027091.msg50208194#msg50208194
Feb 26, 2019 - Community Project - NewEnglandcoin Graphic Redesign Bounty Initiated https://bitcointalk.org/index.php?topic=5027091.msg49931305#msg49931305
Feb 22, 2019 - Dev Policy on Checkpoints on NewEnglandcoin https://bitcointalk.org/index.php?topic=5027091.msg49875242#msg49875242
Feb 20, 2019 - NewEnglandCoin v1.2.1 Released to Secure the Hard Kork https://bitcointalk.org/index.php?topic=5027091.msg49831059#msg49831059
Feb 11, 2019 - NewEnglandCoin v1.2.0 Released, Anti-51% Attack, Anti-instant Mining after Hard Fork https://bitcointalk.org/index.php?topic=5027091.msg49685389#msg49685389
Jan 13, 2019 - Cheetah_CpuMiner added support for CPU Mining on Mac https://bitcointalk.org/index.php?topic=5027091.msg49218760#msg49218760
Jan 12, 2019 - NENG Core v1.1.2 Released to support MacOS OSX Wallet https://bitcointalk.org/index.php?topic=5027091.msg49202088#msg49202088
Jan 2, 2019 - Cheetah_Cpuminer v1.1.0 is released for both Linux and Windows https://bitcointalk.org/index.php?topic=5027091.msg49004345#msg49004345
Dec 31, 2018 - Technical Whitepaper is Released https://bitcointalk.org/index.php?topic=5027091.msg48990334#msg48990334
Dec 28, 2018 - Cheetah_Cpuminer v1.0.0 is released for Linux https://bitcointalk.org/index.php?topic=5027091.msg48935135#msg48935135
Update on Dec 14, 2018 - NENG Blockchain Stuck Issue https://bitcointalk.org/index.php?topic=5027091.msg48668375#msg48668375
Nov 27, 2018 - Exclusive for PC CPU Miners - How to Steal a Block from ASIC Miners https://bitcointalk.org/index.php?topic=5027091.msg48258465#msg48258465
Nov 28, 2018 - How to CPU Mine a NENG block with window/linux PC https://bitcointalk.org/index.php?topic=5027091.msg48298311#msg48298311
Nov 29, 2018 - A Warning to ASIC Miners https://bitcointalk.org/index.php?topic=5027091.msg48324708#msg48324708
Disclosure: Dev Team Came from ShorelineCrypto, a US based Informatics Service Business offering Fee for service for Coin Creation, Coin Exchange Listing, Blockchain Consulting, etc.
submitted by honglu69 to NewEnglandCoin [link] [comments]

08-21 10:34 - 'I finally finished an altcoin with working mining, wallet etc. However when I tried to run a main node on AWS I could not for the life of me get my local client to connect.' (self.Bitcoin) by /u/AthP2121 removed from /r/Bitcoin within 67-77min

'''
I opened all ports on AWS, put in the DNS and public address under “addnode” yet still nothing. Is this a common issue with AWS?
(Please let me know if you want any more details on the project)
'''
I finally finished an altcoin with working mining, wallet etc. However when I tried to run a main node on AWS I could not for the life of me get my local client to connect.
Go1dfish undelete link
unreddit undelete link
Author: AthP2121
submitted by removalbot to removalbot [link] [comments]

Let's connect with each others nodes!

Hey guys so I have my node up and running (finally). And I thought it would be cool to connect to those of you here who are running a full node as well.
If you want to add me just run:
bitcoin-cli addnode "24hhthvtdskpk4gw.onion:8333" "add"
submitted by nerviosus to Bitcoin [link] [comments]

Running a Bitcoin node on a $11.99 SBC

Running a Bitcoin node on a $11.99 SBC
Just wanted to let you guys know that I'm successfully running a (pruned) Bitcoin node + TOR on a $11.99 single board computer (Rock Pi S).
The SBC contains a Rockchip RK3308 Quad A35 64bit processor, 512MB RAM, RJ45 Ethernet and USB2 port and I'm using a 64GB SDCard. It runs a version of Armbian (410MB free). There's a new version available that even gives you 480MB RAM, but I'm waiting for Bitcoin Core 0.19 before upgrading.
To speed things up I decided to run Bitcoin Core on a more powerful device to sync the whole blockchain to an external HDD. After that I made a copy and ran it in pruned mode to end up with the last 5GB of the blockchain. I copied the data to the SD card and ran it on the Rock Pi S. After verifying all blocks it runs very smoothly. Uptime at the moment is 15 days.
I guess you could run a full node as well if you put in a 512GB SDcard.
The Rock Pi S was sold out, but if anybody is interested, they started selling a new batch of Rock Pi S v1.2 from today.
Screenshot of resources being used
Bitcoin Core info
Around 1.5 GB is being transferred every day
---
Some links and a short How to for people that want to give it a try:
  1. This is the place where I bought the Rock Pi S.
  2. Here you find more information about Armbian on the Rock Pi S. Flash it to your SDCard. Follow these instructions.
  3. Disable ZRAM swap on Armbian. If you don't do this eventually Bitcoin Core will crash. nano /etc/default/armbian-zram-config ENABLED=false
  4. Enable SWAP on Armbian sudo fallocate -l 1G /swapfile sudo chmod 600 /swapfile sudo mkswap /swapfile sudo swapon /swapfile sudo swapon --show sudo cp /etc/fstab /etc/fstab.bak echo '/swapfile none swap sw 0 0' | sudo tee -a /etc/fstab
  5. Set up UFW Firewall sudo ufw default deny incoming sudo ufw default allow outgoing sudo ufw allow ssh # we want to allow ssh connections or else we won’t be able to login. sudo ufw allow 8333 # port 8333 is used for bitcoin nodes sudo ufw allow 9051 # port 9051 is used for tor sudo ufw logging on sudo ufw enable sudo ufw status
  6. Add user Satoshi so you don't run the Bitcoin Core as root sudo adduser satoshi --home /home/satoshi --disabled-login sudo passwd satoshi # change passwd sudo usermod -aG sudo satoshi # add user to sudo group
  7. Download (ARM64 version) and install Bitcoin Core Daemon
  8. Download and install TOR (optional). I followed two guides. This one and this one.
  9. Create a bitcoin.conf config file in the .bitcoin directory. Mine looks like this: daemon=1 prune=5000 dbcache=300 maxmempool=250 onlynet=onion proxy=127.0.0.1:9050 bind=127.0.0.1 #Add seed nodes seednode=wxvp2d4rspn7tqyu.onion seednode=bk5ejfe56xakvtkk.onion seednode=bpdlwholl7rnkrkw.onion seednode=hhiv5pnxenvbf4am.onion seednode=4iuf2zac6aq3ndrb.onion seednode=nkf5e6b7pl4jfd4a.onion seednode=xqzfakpeuvrobvpj.onion seednode=tsyvzsqwa2kkf6b2.onion #And/or add some nodes addnode=gyn2vguc35viks2b.onion addnode=kvd44sw7skb5folw.onion addnode=nkf5e6b7pl4jfd4a.onion addnode=yu7sezmixhmyljn4.onion addnode=3ffk7iumtx3cegbi.onion addnode=3nmbbakinewlgdln.onion addnode=4j77gihpokxu2kj4.onion addnode=5at7sq5nm76xijkd.onion addnode=77mx2jsxaoyesz2p.onion addnode=7g7j54btiaxhtsiy.onion ddnode=a6obdgzn67l7exu3.onion
  10. Start Bitcoin Daemon with the command bitcoind -listenonion
Please note that I'm not a professional. So if anything above is not 100% correct, let me know and I will change it, but this is my setup at the moment.
submitted by haste18 to Bitcoin [link] [comments]

Bitcoin core RPC very slow: "mapOrphan overflow, removed 1 tx"

I am running bitcoin core v0.18.0 and noticed that now my queries made locally through the RPC are taking very long. Here is my bitcoin.conf:
txindex=1 datadir=/media/**** maxmempool=30000 mempoolexpiry=99999 choosedatadir=1 checkblocks=3 minrelayfee=0 maxconnections=9999 debug=mempool debug=mempoolrej addnode=*** addnode=*** logips=1 rest=1 rpcuser=*** rpcpassword=*** 
And here is a sample of the log, notice the unusual mapOrphan overflow lines:
20-05-21T21:04:09Z AcceptToMemoryPool: peer=33: accepted 1755b76d790f73252c0ccf890477803aa295444953514fc5c9aad8c2fe6154e0 (poolsz 20383 txn, 105635 kB) 2020-05-21T21:04:09Z stored orphan tx 89cdced1c7c61bf59633af323fd2dbe07c5a6859c51d83247f0fb01b83eb1451 (mapsz 101 outsz 137) 2020-05-21T21:04:09Z mapOrphan overflow, removed 1 tx 2020-05-21T21:04:10Z AcceptToMemoryPool: peer=26: accepted 1122f2315279bc0378fe51733638ede97dcaa938c2fcbd930d91ac2405999fcd (poolsz 20385 txn, 105762 kB) 2020-05-21T21:04:10Z AcceptToMemoryPool: peer=33: accepted 95bd4499ffd3111dab98dbbcb565ff897f21a07c9242659cd38f452022267f78 (poolsz 20386 txn, 105763 kB) 2020-05-21T21:04:10Z stored orphan tx 8c547967ff198c286770f966256c3b09482c5390a93016e597d8a1c6c6699afa (mapsz 101 outsz 138) 2020-05-21T21:04:10Z mapOrphan overflow, removed 1 tx 2020-05-21T21:04:10Z stored orphan tx 2d5fcb835d580caa7fd32f0260cb4ce0e5edf67bf1dc134d1153d6d3118c7009 (mapsz 101 outsz 138) 2020-05-21T21:04:10Z mapOrphan overflow, removed 1 tx 2020-05-21T21:04:10Z AcceptToMemoryPool: peer=20: accepted a49508232092870d58d4f7c63127cb688897d25f8ba1fb0d1c86e4c4b09a2f00 (poolsz 20387 txn, 105764 kB) 2020-05-21T21:04:10Z stored orphan tx 854ccbbd7fd0f04b466dec92df3cbfe96fd8aa25eb0aa17a8524aa82a4bff6ff (mapsz 101 outsz 138) 2020-05-21T21:04:10Z mapOrphan overflow, removed 1 tx 2020-05-21T21:04:10Z stored orphan tx 8ee4f6de0f5d9bdeaa840749193799636b22498711401936e86fc265574430f7 (mapsz 101 outsz 138) 2020-05-21T21:04:10Z mapOrphan overflow, removed 1 tx 
The node is up-to-date and I didn't detect anything unusual (like a stale block/fork).
submitted by johnturtle to BitcoinBeginners [link] [comments]

Solve the "storage, mining pool and exchange centralization", and only generate 1G data every year(only pc-miner)

The blockheader has two segments with a total length of 64 bit0 (of which blocktime is 64 bits), which strongly prevents the collapse effect of the sha256 operation in the ASIC miner, so that the mining difficulty will not increase indefinitely. The centralization for the high hashrate of the mining pool is strongly restricted. Census and prune the transactions (at most 4 outputs per transaction) whose all outputs are spent,in the block below 1300 depth in batches(i.e. clear up the input and output at the same time, and only keep the version of all-outs-spent transaction on the disk,--not serialize vin and vout). 250 for each batch, 20 block files(one file per block) will be reconstructed for each block received from other nodes, that is to say, 5000 transactions will be pruned at a time. And special mechanism is used to make the synchronization of data from malicious nodes error free. Only 1G data is increased every year. The data it running for 1000 years will be no more than 1T. Block size is 2M, and only 1g data is increased every year without SPV, which strongly prevents the storage of a large number of block data reducing the number of nodes. At the same time, 'four outputs per tx' limit the settlement of the mining pool, and strongly prevent the centralization of the mining pool. For example, the settlement is sent to 4000 miners, which requires 1000 transactions. All currencies are locked in the maturity of 300 blocks (the input can only be used as prevout after 300 blocks), which strongly prevents the frequency of trading speculation, the crash from the online exchange, and prevent the centralization of the biggest online exchange in the world.
This has achieved "absolute decentralization".
At present, the tip height is only 600, and there is no pre-mined. The RPC is stable and reliable same as bitcoin 0.10.2. No segwit but P2SH, a little change based on 0.10.2. Usage: $ /download-directory/bitcoind -addnode =47.114.58.108 (same for Ubuntu) with bitcoin.conf configuration file
Detailed introduction,original text is as follows: github-holyangel250-bitsupercoin
submitted by DangerousDetail8 to BitcoinMining [link] [comments]

Solve the "storage, mining pool and exchange centralization", and only generate 1G data every year

The blockheader has two segments with a total length of 64 bit0 (of which blocktime is 64 bits), which strongly prevents the collapse effect of the sha256 operation in the ASIC miner, so that the mining difficulty will not increase indefinitely. The centralization for the high hashrate of the mining pool is strongly restricted. Census and prune the transactions (at most 4 outputs per transaction) whose all outputs are spent,in the block below 1300 depth in batches(i.e. clear up the input and output at the same time, and only keep the version of all-outs-spent transaction on the disk,--not serialize vin and vout). 250 for each batch, 20 block files(one file per block) will be reconstructed for each block received from other nodes, that is to say, 5000 transactions will be pruned at a time. And special mechanism is used to make the synchronization of data from malicious nodes error free. Only 1G data is increased every year. The data it running for 1000 years will be no more than 1T. Block size is 2M, and only 1g data is increased every year without SPV, which strongly prevents the storage of a large number of block data reducing the number of nodes. At the same time, 'four outputs per tx' limit the settlement of the mining pool, and strongly prevent the centralization of the mining pool. For example, the settlement is sent to 4000 miners, which requires 1000 transactions. All currencies are locked in the maturity of 300 blocks (the input can only be used as prevout after 300 blocks), which strongly prevents the frequency of trading speculation, the crash from the online exchange, and prevent the centralization of the biggest online exchange in the world.
This has achieved "absolute decentralization".
At present, the tip height is only 600, and there is no pre-mined. The RPC is stable and reliable same as bitcoin 0.10.2. No segwit but P2SH, a little change based on 0.10.2. Usage: $ /download-directory/bitcoind -addnode =47.114.58.108 (same for Ubuntu) with bitcoin.conf configuration file
Detailed introduction,original text is as follows: github-holyangel250-bitsupercoin
submitted by DangerousDetail8 to BitcoinSerious [link] [comments]

Solve the "storage, mining pool and exchange centralization", and only generate 1G data every year

The blockheader has two segments with a total length of 64 bit0 (of which blocktime is 64 bits), which strongly prevents the collapse effect of the sha256 operation in the ASIC miner, so that the mining difficulty will not increase indefinitely. The centralization for the high hashrate of the mining pool is strongly restricted. Census and prune the transactions (at most 4 outputs per transaction) whose all outputs are spent,in the block below 1300 depth in batches(i.e. clear up the input and output at the same time, and only keep the version of all-outs-spent transaction on the disk,--not serialize vin and vout). 250 for each batch, 20 block files(one file per block) will be reconstructed for each block received from other nodes, that is to say, 5000 transactions will be pruned at a time. And special mechanism is used to make the synchronization of data from malicious nodes error free. Only 1G data is increased every year. The data it running for 1000 years will be no more than 1T. Block size is 2M, and only 1g data is increased every year without SPV, which strongly prevents the storage of a large number of block data reducing the number of nodes. At the same time, 'four outputs per tx' limit the settlement of the mining pool, and strongly prevent the centralization of the mining pool. For example, the settlement is sent to 4000 miners, which requires 1000 transactions. All currencies are locked in the maturity of 300 blocks (the input can only be used as prevout after 300 blocks), which strongly prevents the frequency of trading speculation, the crash from the online exchange, and prevent the centralization of the biggest online exchange in the world.
This has achieved "absolute decentralization".
At present, the tip height is only 600, and there is no pre-mined. The RPC is stable and reliable same as bitcoin 0.10.2. No segwit but P2SH, a little change based on 0.10.2. Usage: $ /download-directory/bitcoind -addnode =47.114.58.108 (same for Ubuntu) with bitcoin.conf configuration file
Detailed introduction,original text is as follows: github-holyangel250-bitsupercoin
submitted by DangerousDetail8 to altcoin_news [link] [comments]

Bitcoin core configuration in Windows

I've installed Bitcoin Core on Windows with the installer. I don't know how to increase the number of connections. Currently, it's always 8.
Several sources on the internet claim that custom configuration belong to a bitcoin.conf in the AppData/Bitcoin directory. But that doesn't work for me. I tried. In fact, I found out that the configuration including the datadir is currently contained in the registry. Not a single source I could found tells me that the registry contains these config values, so I'm kinda bummed out by this.
In any case, does that mean that I have to add a config value in the registry? And if so, how? The config names are different, namely, the registry config names are in camel case, while the names in bitcoin.conf are like "maxconnections=150". Help!
Edit: I consider the possibility that using the bitcoin.conf actually works and I made a mistake.
Edit2: Only 8 outgoing connections are possible (without addnode), so I opened the firewall as suggested.
Edit3: I finally get incoming connections. It's still slow but I'm optimistic that the speed will increase. It almost feels like synching an Ethereum node ffs.
Edit4: After having had 16 peers at some point yesterday, I'm back to 8 peers and no incoming connections. Speed is 1.3% per hour.
Edit5: I'm under the impression that I simply underestimated the size of the blockchain. I'm used to download huge files within minutes but 200gb is certainly something else. My bandwidth doesn't seem to be used to its full extent but it spikes up to the maximum throughput from time to time, so I guess this is the limiting factor after all. And some people want even larger blocks? F*** that.
submitted by HelloImRich to Bitcoin [link] [comments]

No inbound connections on my bitcoin full node with TOR

update: it's ok now, it only required some time. Also, looking at debug.log it won't show anything about inbound connections as I thought, it must be used `bitcoin-cli getpeerinfo` in order to get all the connections info (inbound + outbound)
Can someone connect to my node? u3ob433qu3ebkmsu.onion:8333
I'm behind a CG-NAT so I thought to use TOR to overcame it but still I have outbound connections but no inbound.
$ bitcoin-cli getnetworkinfo
{ "version": 180000, "subversion": "/Satoshi:0.18.0/", "protocolversion": 70015, "localservices": "000000000000040c", "localrelay": true, "timeoffset": 0, "networkactive": true, "connections": 10, "networks": [ { "name": "ipv4", "limited": true, "reachable": false, "proxy": "127.0.0.1:9050", "proxy_randomize_credentials": true }, { "name": "ipv6", "limited": true, "reachable": false, "proxy": "127.0.0.1:9050", "proxy_randomize_credentials": true }, { "name": "onion", "limited": false, "reachable": true, "proxy": "127.0.0.1:9050", "proxy_randomize_credentials": true } ], "relayfee": 0.00001000, "incrementalfee": 0.00001000, "localaddresses": [ { "address": "u3ob433qu3ebkmsu.onion", "port": 8333, "score": 4 } ], "warnings": "" } 
bitcoin.conf
server=1 daemon=1 # RPC rpcuser=***** rpcpassword=******* # TOR onlynet=onion proxy=127.0.0.1:9050 bind=127.0.0.1 dnsseed=0 dns=0 addnode=nkf5e6b7pl4jfd4a.onion addnode=yu7sezmixhmyljn4.onion # Raspberry Pi optimizations dbcache=100 maxorphantx=10 maxmempool=50 maxconnections=40 maxuploadtarget=5000 prune=6000 
submitted by LiL0u to Bitcoin [link] [comments]

Addnode vs Connect

Addnode vs Connect
Hello everyone, i would like to share the differences between two commands (Addnode vs connect) which are used to find connections.
Addnode:
Let's you establish a connection to a particular node as well as let other nodes connected to it know you exist.
Connect:
Using this will only let you connect to that specific node and nothing else.

Recommended command if you're behind a firewall or have trouble finding connections. is addnode=xx.xx.xx.xx
x is the address of the node.Enter these node in the x42.conf file.
Popular nodes for x42
addnode=52.211.235.48:52342
addnode=18.179.72.204:52342
addnode=63.32.82.169:52342
addnode=34.255.35.42:52342
Source : https://github.com/bitcoin/bitcoin/blob/masteshare/examples/bitcoin.conf
https://preview.redd.it/t6mv6dbh7qd41.png?width=1417&format=png&auto=webp&s=8b138662a256c3515c57c9efb6c2fb78eb62560d
submitted by sirviks to x42 [link] [comments]

Reindexing my Bitcoin Cash blockchain fails at block 264084

My BUCash was seemingly chugging along fine but for the sake of it I decided to reindex. It seems to have processed all of the block files (with a lot of out-of-order blocks, is that normal?) but now I guess it's trying to validate block 264084 over and over but all my debug is showing me about it something similar to this every time:
2017-08-04 23:17:03 Initial headers were either not received or not received before the timeout - disconnecting peer=46.166.128.184:8333 (31) 2017-08-04 23:17:03 disconnecting peer 46.166.128.184:8333 (31) 2017-08-04 23:17:03 initial getheaders (264082) to peer=185.21.216.183:8333 (33) (startheight:479092) 2017-08-04 23:17:03 sending: getheaders (997 bytes) peer=33 2017-08-04 23:17:03 received: headers (162003 bytes) peer=33 2017-08-04 23:17:03 ERROR: AcceptBlockHeader: block 0000000000000015e1d0d782b4dc0f8e2f098d0396cf85ca1893c0e6af338a43 height 264084 is marked invalid 2017-08-04 23:17:03 ERROR: invalid header received 2017-08-04 23:17:03 ProcessMessages(headers, 162003 bytes) FAILED peer=33 
The only other similar thing I found was this guy having issues with the exact same block: https://np.reddit.com/BitcoinABC/comments/6omaqm/block_264084_possible_timewarp_problem/
PMing him revealed that he was unable to fix it and simply no longer runs a node.
Can anyone help me out here? Should I just redownload the blockchain?
submitted by suchCow to btc [link] [comments]

I joined the full node club as well

Anything else I can do? I run the node all the time except when I sleep, since I turn my computer off when I sleep. I currently have 21 active connections, does adding more connections help? If so, how can I do that?
submitted by zimmah to btc [link] [comments]

Bitcoin 1776 Software ready to mine

Anyone interested in mining Bitcoin 1776 can do so here. Very easy to mine, do it on your home computer :
https://www.bitcoin1776.org/downloads.html
Once you install the software:
Go to the top menu, "Help" -> "Debug Window"
Select "Console"
Paste
addnode "144.168.39.239:6703" "add"
addnode "192.227.186.69:6703" "add"
addnode "192.227.186.70:6703" "add"
And hit enter. On the "Peers" tab next to "Console", you should see Bitcoin1776 (instead of Satoshi...) popup sometime in the next few minutes (maybe 10 minutes). After which, we will be connected to each other and our IP addresses saved.
Opening ports to mine using Bitcoin 1776 software
https://imgur.com/a/gQqtpyw
Trouble with Mining Helper
https://www.reddit.com/Bitcoin1776/comments/9rmfh8/trouble_with_mining_helpe
To mine blocks and get 0.25 Kennedy coins, in that same Console, type
generate 1 2000000000
https://drive.google.com/open?id=1ne1975WpqwjQrfAHIT9inGC4OW7zvTPi
submitted by Bitcoin1776 to Bitcoin1776 [link] [comments]

A tour of the Gridcoin wallet

Hey guys, I thought I would put together an in-depth tour of the Gridcoin wallet software for all of our recent newcomers. Here I'll be outlining all the features and functions the windows GUI wallet has to offer, along with some basic RPC command usage. I'll be using the windows wallet as an example, but both linux and macOS should be rather similar. I'll be including as many pictures as I can as embedded hyperlinks.
Edit: Note that since I originally made this there has been a UI update, so your client will be different colors but all the button locations are in the same place.
This is my first post like this, so please forgive me if this appears a little scatter-brained.
This will not cover the mining setup process for pool or solo miners.
When you launch the wallet software for the first time you should be greeted with this screen.

OVERVIEW TAB

After that prompt, you should be left sitting on the main overview tab with several fields on it.
From top to bottom:

SEND TAB

Now onto the other tabs on the left side. Currently we're on the Overview tab, lets move down to the Send tab. This tab it pretty self-explanatory, you use it if you want to send coins, but I'll go over the fields here:
  • Pay To: Enter a valid gridcoin address to send coins too. Gridcoin addresses always start with an S or and R.
  • Label: Enter a label here and it will put that address in your "address book" under that label for later use. You can leave it blank if you don't want it in your address book.
  • Message: Enter a message here if you want it attached to your transaction.
  • Amount: How many coins you want to send.
  • Add Attachment: Leave this alone, it is broken.
  • Track Coins: This doesn't do anything.

RECEIVE TAB

Now down to the Receive tab. Here you should have a single address listed. If you double click on the label field, you can edit it's label.
  • New: Generate a new address.
If you click on an address, the rest of the options should be clickable.
  • Copy: Copy the selected address to your clipboard.
  • Show QR Code: Show a scan-able QR code for the selected address.
  • Sign Message: Cryptographically sign a message using the selected address.

TRANSACTIONS TAB

The Transactions tab is pretty boring considering we have no transactions yet. But as you can see there are some sorting tools at the top for when you do have transactions listed.

ADDRESS BOOK TAB

The Address Book is where all the addresses you've labeled (that aren't yours) will show up.
  • Verify Message: Verifies a message was signed by the selected address.
The rest of the functions are similar to the functions on the Receive tab.

VOTING TAB

Onto the Voting tab. There wont be any polls because we aren't in sync yet.
  • Reload Polls: Pretty self-explanatory, I've never had to use this.
  • Load History: By default, the wallet will only display active polls. If you want to view past polls you can use this.
  • Create Poll: You can create a network-wide poll. You must have 100,000 coins as a requirement to make a poll. (Creating a poll does not consume the coins)
Here's what the Voting tab will look like once you're in sync

CONTEXT BAR

Now onto the context bar menus on the top.
Under File you have:
  • Backup Wallet/Config: This lets you backup your wallet configuration file just in case.
  • Export: You can export your Transactions tab or Address Book in CSV format.
  • Sign message: Does the same thing as on the Receive tab.
  • Verify message: Does the same thing as on the Address Book tab.
  • Exit: Close the wallet.
Under Settings you have:
  • Encrypt Wallet: Encrypts your wallet with a password. (we'll come back to this)
  • Change Passphrase: Allows you to change your encryption password.
  • Options: Opens the options menu. (We'll come back to this)
Under Community you have:
Under Advanced you have:
  • Advanced Configuration: Opens the Advanced Configuration menu. (Not so advanced if you ask me)
  • Neural Network: Allows you to view solo miners project statistics. It will be largely blank if you're not in sync yet.
  • FAQ: Don't touch this, It is broken.
  • Foundation: Don't touch this, It is broken.
  • Rebuild Block Chain: Starts the client syncing from 0. Don't worry, using this will not make you lose coins.
  • Download Blocks: Downloads the latest official snapshot, can help speed up syncing. The download progress tends to sit at 99.99% for a long time, don't worry, it's working.
Under Help you have:
  • Debug window: Opens the debug window. (We'll come back to this)
  • Diagnostics: Don't touch this, it is broken. This has since been fixed. You can use this to see if there is anything wrong with your setup.
  • About Gridcoin: Opens the About Dialog. This gives you your client version and other information.

OPTIONS

Now back to the options menu under Settings > Options.
Here we have the options menu main tab:
  • Pay transaction fee: The transaction fee that will be automatically paid when you make a transaction.
  • Reserve: You can reserve an amount so that it will always be available for spending.
  • Start Gridcoin on system login: Pretty self-explanatory
  • Detach databases at shutdown: Speeds up shutdown, but causes your blockchain file to no longer be portable.
On the Network tab:
  • Map port using UPnP: Attempts to connect to nodes through UPnP.
  • Connect through SOCKS proxy: Allows you to connect through a proxy.
The window tab is pretty self-explanatory.
The Display tab is also pretty self-explanatory, with the exception of:
  • Display coin control features (experts only!): This allows you to have a great deal of control over the coins in your wallet, check this for now and I'll explain how to use it further down. Don't forget to click "Apply".

ENCRYPTING YOUR WALLET

Now that all of that is out of the way. The first thing you'll want to do is encrypt your wallet. This prevents anybody with access to your computer from sending coins. This is something I would recommend everyone do.
Go to Settings > Encrypt Wallet and create a password. YOU CANNOT RECOVER YOUR COINS IF YOU FORGET YOUR PASSWORD.
Your wallet will close and you will have to start it up again. This time when it opens up, you should have a new button in the bottom left. Now if you want to stake you will have to unlock your wallet. Notice the "For staking only" box that is checked by default. If you want to send a beacon for solo mining or vote, you will need to uncheck this box.

GETTING IN SYNC AND ICONS

Before we continue, Let's wait until we're in sync. Depending on your internet speeds, this could take from several hours to over a day or 2. This can be sped up by using Advanced > Download Blocks, but this can still take several hours.
This is what an in-sync client should look like. Notice the green check to the right of the Receive tab. All of these icons give you information when you hover your mouse over them.
The lock
The arrow tells you if you're staking. If you aren't staking, it will tell you why you're not staking. If you are staking it will give you an estimated staking time. Staking is a very random process and this is only an estimate, not a countdown.
The connection bars tell you how many connections to the network you have.
The check tells you if you're in sync.

WHAT IS STAKING?

Now I've said "stake" about a million times so far and haven't explained it. Gridcoin is a Proof of Stake (PoS) coin.
Unlike bitcoins Proof of Work (PoW), PoS uses little system resources, so you can use those resources for scientific work. PoS works by users "Staking" with their balance. The higher the balance, the higher the chance to create, or "stake" a block. This means you need to have a positive balance in order to stake. Theoretically, you can stake with any amount over 0.0125 coins, but in practice it's recommended to have at least 2000 coins to reliably stake.
Staking is important for solo miners, because they get paid when they stake. Pool miners don't need to stake in order to get paid however. So if you want to solo mine, you'll need to buy some coins from an exchange or start in the pool first and move to solo when you have enough coins.
In addition to Research Rewards for miners, anyone who holds coins (solo miners, pool miners, and investors) gets 1.5% interest annually on top of your coins. So it can be beneficial for pool miners to stake as well.
Here is a snippet of what a research rewards transaction looks like from my personal wallet. I have a label on that address of "Payout address" as you can see here.

UTXOS AND COIN CONTROL

At this point you'll need some coins. You can use one of our faucets like this one or this one to test coin control out.
First let me explain what a UTXO is. UTXO stands for Unspent Transaction Output. Say you have an address with 0 coins in it, and someone sends you 10 coins like I've done here. Those 10 coins are added to that address in the form of a UTXO, so we have an address with one 10 coin UTXO in it.
Now we receive another 5 coins at the same address, like so. Now we have an address with one 10 coin UTXO and one 5 coin UTXO. But how do we view how our addresses are split up into different UTXOs?
Earlier we checked the "Display coin control features" box in Settings > Options > Display. Once that's checked you'll notice there's another section in the Send tab labeled "Coin Control Features". If you click the "Inputs" button, you'll get a new window. And look, there's our 2 UTXOs.
All UTXOs try to stake separately from each other, and remember that the chance a UTXO has to stake is proportional to it's size. So in this situation, my 10 coin UTXO has twice the chance to stake as my 5 coin UTXO. Now wallets, especially ones that make a lot of transactions, can get very fragmented over time. I've fragmented my wallet a little so I can show you what I'm talking about.
How do we clean this up? We can consolidate all this into one UTXO by checking all the boxes on the left and selecting OK.
Now pay attention to the fields on the top:
  • Quantity: The total amount of UTXOs we have selected.
  • Amount: The total amount of coins we have selected.
  • Fee: How much it would cost in fees to send all those UTXOs (more UTXOs = more transaction data = more fees)
  • After Fee: Amount - Fees.
  • Bytes: How large the transaction is in bytes.
  • Priority: How your client would prioritize making a transaction with this specific set of UTXOs selected had you not used coin control.
  • Low Output: If your transaction is less than 0.01 coins (I think).
  • Change: What you will get back in change.
  • custom change address: You can set the address you get your change back at, by default it will generate a new address.
So let's fill out our transaction so we end up with 1 UTXO at the end.
In "Pay To:" Just put any address in your wallet, and for the amount put what it has listed in the "After Fee" Field. Just like this.
Notice how we get no change back.
Now click "Send", we'll be prompted to enter our passphrase and we're asked if we want to pay the fee, go ahead and click "Yes".
Now if we go back to the Overview tab we get this funky icon. If you hover your mouse over it, it says "Payment to yourself", and the -0.0002 GRC is the network transaction fee.
(Ignore the first one, that was me fragmenting my wallet)
Now if we look at the Coin Control menu, we can see that we've slimmed our wallet down from 7 UTXOs to 1.
Now why would you want to use coin control?
2 Situations:
  1. UTXOs less than 0.0125 coins cannot stake. So you can combine a lot of tiny, useless UTXOs into 1 bigger one that can stake.
  2. After a UTXO stakes, it cannot stake for another 16 hours. So if you have 1 large UTXO that is big enough to stake more than once every 16 hours, you can split it into smaller UTXOs which can allow you to stake slightly more often.
  3. By default, the wallet will always generate a new address for change, which can make your wallet get very messy if you're sending lots of transactions. Keep in mind that more UTXOs = larger transactions = more fees.
Sidenote - When you stake, you will earn all research rewards owed reguardless of which UTXO staked. However, you'll earn the 1.5% interest for that UTXO. Not your whole wallet.

FORKING

A fork is when the network splits into multiple chains, with part of the network on each chain. A fork can happen when 2 blocks are staked by different clients at the same time or very close to the same time, or when your client rejects a block that should have been accepted due to a bug in the code or through some other unique circumstance.
How do I know if I'm on a fork?
Generally you can spot a fork by looking at the difficulty on your Overview tab. With current network conditions, if your difficulty is below 0.1, then you're probably on a fork.
You can confirm this by comparing your blockhash with someone elses, like a block explorer.
Go to [Help > Debug Window > Console]. This is the RPC console, we can use to do a lot of things. You can type help to get a list of commands, and you can type help [command you need help with] (without the brackets) to get information on a command. We'll be using the getblockhash [block number] command.
Type getblockhash [block number] in the console, but replace [block number] with the number listed next to the "Blocks:" field on the Overview tab.
This will spit out a crazy string of characters, this is the "blockhash" of that block.
Now head over to your favorite block explorer, I'll be using gridcoinstats. Find the block that you have the hash for, use the search bar or just find it in the list of blocks.
Now compare your hash with the one gridcoinstats gives you. Does it match?
If it matches, then you're probably good to go. If it matches but you still think you're on a fork, then you can try other block explorers, such as gridcoin.network or neuralminer.io.
If it doesn't match, then you need to try to get off that fork.
How do I get off a fork?
  1. Just wait for an hour or two. 95% of the time your client is able to recover itself from a fork given a little time.
  2. Restart the client, wait a few minutes to see if it fixes itself. If it doesn't restart again and wait. Repeat about 4 or 5 times.
  3. Find where the fork started. Using the getblockhash command, go back some blocks and compare hashes with that on a block explorer so you can narrow down what the last block you and the block explorer had in common. Then use reorganize [the last block hash you had in common]. Note that reorganize takes a blockhash, not a block number.
  4. Use Advanced > Download Blocks.
  5. If none of this works, you can take a look at social media (reddit/steemit) and see what other people are saying.

CONFIGURATION FILE

Your configuration file depends on your operation system:
  • On Windows: %appdata%\GridcoinResearch\
  • On Linux: ~/.GridcoinResearch/
  • On MacOS: /Users/USERNAME/Library/Application/Support/GridcoinResearch/
And it should look like this.
If you open up your gridcoinresearch.conf, you'll see the default one it generated. Note that if you entered your email earlier, the first line will have your email on it instead of "investor". If you decided you want to solo mine but didn't enter your email when you first started the wallet, go ahead and put your email on the first line in place of "investor". If you're a pool miner, just leave it as "investor".
Next, it's recommended that you use the addnodes on the gridcoin wiki. So our gridcoinresearch.conf will look like this.
A useful line for solo miners is PrimaryCPID=[YOUR CPID]. Sometimes your wallet can pick up on the wrong CPID so it's good to have that in there if you're solo mining.

RUNNING A LISTENING NODE

A listening node is a node that listens for blocks and transactions broadcasted from nodes and forwards them on to other nodes. For example, during the syncing process when you're getting your node running for the first time, you're downloading all the blocks from listening nodes. So running a listening node helps support the network.
Running a gridcoin listening node is simple. All you need to do is add listen=1 to your gridcoinresearch.conf and you need to forward port 32749 on your router.
If you don't know how to port forward, I'd suggest googling "How to port forward [your router manufacturer]".

QUICK LINKS

Gridcoin.us Official Website
Gridcoin.science Unofficial Website
Gridcoinstats.eu Block Explorer
NeuralMiner.io Block Explorer
Gridcoinstats.eu Faucet
Gridcoin.ch Faucet
Gridcoin Wiki
Gridcoin Github
GRCPool
Arikado Pool
And that's all I have for now!
I plan to keep this post up-to-date with changes in the client. So if anyone has any suggestions, have clarifications they want made, or maybe I got something wrong, then please feel free to leave a comment below or PM me!
submitted by Personthingman2 to gridcoin [link] [comments]

Gridcoin Leisure Update 3.7.14.0 Released

Today we have a new leisure update for you. This version includes a lot of "under the hood" changes, but there are some improvements for the average user as well.
 
Notably this release includes a better time to stake calculation method, thanks to @jamescowens. Also the Neural Network runs much smoother thanks to many optimizations by @ifoggz.
 
Download the update from GitHub here.
The Windows MSI can be downloaded here.
 
Full Release Notes:
Added
 
Changed
 
Fixed
 
Removed
 
Thank you to all the developers who contributed to this release. I will update this post when the Windows MSI has been uploaded to the website.
submitted by barton26 to gridcoin [link] [comments]

PIVX Core Wallet 3.0.5 final release (November 13th, 2017) - Mandatory Upgrade

Github release link
Forum Post

Important Notes

Upgrade instructions

1- Download the appropriate release for your platform from the Github release link. For command line installs/updates this link may help.
2- Start up your client and see if you are on the wrong chain by using this link (Am I forked?) or manually comparing your latest block hash against the [block explorer](www.presstab.pw/phpexplorePIVX/index.php#)
3- If you are on the correct chain, let it fully sync (or as far as it will go) and then repeat step 2. If you are still on the right chain move on to step 4. If you're on the wrong chain, download the chainstate from this link (mirror) and follow the instructions to install it. Do NOT delete wallet.dat or your backups folder. Once this is done, restart your client and let it finish syncing
  1. stop your wallet and/or daemon
  2. locate the folder with the blockchain folders (usually ~/.pivx/)
  3. do a complete(!) backup of this folder in case something goes wrong
  4. completely remove the folders "blocks", "chainstate", "sporks" and "zerocoin"
  5. download one of the snapshot-files (preferably the newest one) above into this folder
  6. unpack the snapshot file: 'unzip '
  7. the folders deleted above are now replaced by the ones from the snapshot
  8. restart your wallet and/or daemon
4- On this step you should be fully synced and on the right chain. Using the debug screen or pivx-cli, use the command
spork show 
to output your spork status. Have a look at spork 16 and make sure the value is 1510179528 (now 1609459199). If it is, go ahead and start staking.
If you are having trouble getting the correct value for spork 16, try adding nodes to your pivx.conf file that are protocol 70912. A list of 70912 nodes can be found at http://www.presstab.pw/phpexplorePIVX/nodes.php . This can be done from the debug menu or with pivx-cli by saying
addnode 123.45.67.89 add 

Notable Changes

libzerocoin Exploit Fix

zPIV relies on a 3rd party library called libzerocoin. All currencies that utilize the zerocoin protocol use libzerocoin, and many of those currencies have been exposed to an exploit which allowed for the creation of multiple zero-knowledge spending proofs for one single zerocoin mint. The PIVX developers were able properly identify the exploit, track down any fraudulent spending proofs, link the fraudulent spending proofs with their one valid proof that they were mutated from, and remove any mints from the accumulators that were derived from the invalid spends.

zPIV Maintenance Mode Spork

Handling the above noted libzerocoin exploit required the PIVX team to immediately release a patched wallet to as many users as possible which rejected bad spends and also disabled all zPIV transactions in general. The process of releasing a patched wallet in such a small time frame is frustrating and difficult for all members of the PIVX team and especially users of PIVX. The PIVX developers have added a new spork which allows for zPIV transacting to be turned on/off without having to release a patched wallet. This will allow much smoother operation if any problems occur in the future, and should also allow exchanges and 3rd party services to continue to operate even if zPIV is in maintenance mode.

Accumulator Code Refactor

The zPIV accumulator code has undergone a major refactor. Accumulators are one of the most essential components of the zerocoin protocol, and also one of the most computationally expensive parts of the protocol. This refactoring speeds up syncing and spending of zPIV by over 5x. The new code also allows for spending of zPIV with only 2 required mints occurring on the network after your mint has been added, whereas before 3 were required. This refactor allows for lighter resource load and a smoother user experience.

Money Supply Indexing

The exploit in libzerocoin threw off some of the wallet's internal money supply calculations for both the zPIV supply and the PIV supply. User's wallet's will automatically recalculate the supply on block 908001. User's also have the ability to recalculate supply using the startup flag reindexmoneysupply.

More Extensive Tracking of zPIV Supply Through RPC

More information has been added to the getinfo and getblock RPC calls, which now display the total zPIV supply as well as the balance for each zPIV accumulator.

Multisig GUI

Provides functionality which is currently only available through raw transactions. Multisignature addresses require signatures from multiple parties before coins belonging to the address are spent. Accessed through the File dropdown menu.

Credits

FAQ

  • Will I lose piv or zpiv?
    • No. Backup your wallet.dat again for good measure and never delete a wallet.dat file.
  • My wallet is stuck on block ?
    • Check if you're forked (Am I forked?) and then check if you're really on v3.0.5. If you're on the right version and chain, just hang tight and your wallet will find a good node to sync with eventually. Contact support if it's more than a few hours and the problem persists
  • My zPIV balance is incorrect
    • Contact support in discord or via the Support Portal. Please note that during the upgrade period and zerocoin maintenance mode there may be delays.
submitted by turtleflax to pivx [link] [comments]

such beginner shibe thread wow how to get coin

 how to shibecoin v rich in minutes much instruct so simple any doge can do 

START HERE

UPDATE 1/21/14: I'm not updating this guide anymore. Most of the steps should still work though. See the wiki or check the sidebar for updated instructions.
Before you do anything else, you need to get a wallet. Until there's a secure online wallet, this means you need to download the dogecoin client.
Now open the client you just downloaded. You'll be given a default address automatically, and it should connect to peers and start downloading the dogechain (aka blockchain in formal speak). You'll know because there will be a progress bar at the bottom and at the lower right there should be a signal strength icon (TODO: add screenshots).
If you've waited 2 or 3 minutes and nothing is happening, copy this:
maxconnections=100 addnode=95.85.29.144 addnode=162.243.113.110 addnode=146.185.181.114 addnode=188.165.19.28 addnode=166.78.155.36 addnode=doge.scryptpools.com addnode=doge.netcodepool.org addnode=doge.pool.webxass.de addnode=doge.cryptopool.it addnode=pool.testserverino.de addnode=doge.luckyminers.com addnode=doge.cryptovalley.com addnode=miner.coinedup.comdoge addnode=doge.cryptoculture.net addnode=dogepool.pw addnode=doge.gentoomen.org addnode=doge.cryptominer.net addnode=67.205.20.10 addnode=162.243.113.110 addnode=78.46.57.132 
And paste it into a new text file called dogecoin.conf, which you then place into the dogecoin app directory.
Now restart your qt client and the blockchain should start downloading in about 1-2 minutes.
Once it finished downloading, you're ready to send and receive Dogecoins!

GETTING COINS

Decide how you want to get Dogecoin. Your options are:
I'll go into detail about each of these. I'm currently writing this out. I'll make edits as I add sections. Suggestions are welcome.

MINING

Mining is how new dogecoins are created. If you're new to crypto currencies, read this. To mine (also called "digging"), a computer with a decent GPU (graphics card) is recommended. You can also mine with your CPU, but it's not as efficient.

GPU MINING

These instructions cover only Windows for now. To mine, you'll need to figure out what GPU you have. It'll be either AMD/ATI or Nvidia. The setup for both is approximately the same.

Step One: Choose a pool

There's a list of pools on the wiki. For now it doesn't really matter which one you choose. You can easily switch later.
NOTE: You can mine in two ways. Solo mining is where you mine by yourself. When you find a block you get all the reward. Pool mining is when you team up with other miners to work on the same block together. This makes it more likely that you'll find a block, but you won't get all of it, you'll have to split it up with others according to your share of the work. Pool mining is recommended because it gives you frequent payouts, because you find more blocks. The larger the pool you join, the more frequent the payouts, but the smaller the reward you get.
Over a long period of time the difference between pool and solo mining goes away, but if you solo mine it might be months before you get any coins.

Step two: Set up pool account

The pool you chose should have a getting started page. Read it and follow the instructions. Instructions vary but the general idea is:
When you're done with this, you'll need to know:

Step three: Download mining software

For best performance you'll need the right mining software.
Unzip the download anywhere you want.

Step four: Set up miner

Create a text file in the same folder as your miner application. Inside, put the command you'll be running (remove brackets).
For AMD it's cgminer.exe --scrypt -o stratum+tcp://: -u -p
For Nvidia it's cudaminer.exe -o stratum+tcp://: -O :
Substitute the right stuff in for the placeholders. Then on the next line of the text file type pause. This will let you see any errors that you get. Then save the file with any name you want, as long as the file extension is .bat. For example mine_serverName.bat.

Step five: Launch your miner

Just open the .bat file and a command line window should pop up, letting you know that the miner is starting. Once it starts, it should print out your hash rate.
If you now go to the pool website, the dashboard should start showing your hashrate. At first it'll be lower than what it says in the miner, but that's because the dashboard is taking a 5 minute average. It'll catch up soon enough.
NOTE: A normal hashrate is between 50 Kh/s up to even 1 Mh/s depending on your GPU.

You're now mining Dogecoins

That's it, nothing more to it.

CPU MINING

CPU mining isn't really recommended, because you'll be spending a lot on more on power than you'd make from mining Dogecoin. You could better spend that money on buying Dogecoin by trading. But if you have free electricity and want to try it out, check out this informative forum post.

Trading

Trading has been difficult so far, but Dogecoin just got added to a few new exchanges. If you don't have a giant mining rig, this is probably the best way to get 100k or more dogecoins at the moment. I'll write up a more complete guide, but for now check out these sites:

Faucets

Faucets are sites that give out free coins. Usually a site will give out somewhere between 1 and 100 Dogecoin. Every site has its own time limits, but usually you can only receive coins once every few hours, or in some cases, days. It's a great way to get started. All you do is copy your address from the receive section of your wallet and enter it on some faucet sites. Check out /dogecoinfaucets for more. If you go to each site on there you might end up with a couple hundred Dogecoin!

Begging

This method is pretty straightforward. Post your receiving address, and ask for some coins. Such poor shibe. The only catch is, don't do it here! Please go to /dogecoinbeg.

Tips

At the moment there are two tip bots:
Other redditors can give you Dogecoin by summoning the tip bot, something like this:
+dogetipbot 5 doge
This might happen if you make a good post, or someone just wants to give out some coins. Once you receive a tip you have to accept it in a few days or else it'll get returned. Do this by following the instructions on the message you receive in your inbox. You reply to the bot with "+accept". Commands go in the message body. Once you do that, the bot will create a tipping address for you, and you can use the links in the message you receive to see your info, withdraw coins to your dogecoin-qt wallet, see your history, and a bunch of other stuff.
As a bonus, so_doge_tip has a feature where you can get some Dogecoins to start with in exchange for how much karma you have. To do this, send the message "+redeem DOGE" to so_doge_tip. You'll need to create a tipping account if you don't have one.
If you want to create a tipping account without ever being tipped first, message either of the bots with "+register" and an address will be created for you.

CHANGELOG

  • 1/21/14 - Added note about this thread no longer being updated
  • 1/21/14 - Changed wallet links to official site
  • 12/27/13 - Added 1.3 wallet-qt links
  • 12/21/13 - Added new windows 1.2 wallet link
  • 12/20/13 - Fixed +redeem text
  • 12/18/13 - Added short blurb on trading.
  • 12/18/13 - Updated cudaminer to new version (cudaminer-2013-12-18.zip).
  • 12/18/13 - Fixed +redeem link
  • 12/18/13 - Updates dogecoin.conf, from here.
  • 12/17/13 - Linked to mining explanation.
  • 12/17/13 - Added link to CPU mining tutorial, in response to this.
  • 12/16/13 - Added links to tip commands, link to dogetipbot wiki.
  • 12/16/13 - Note about tip commands going in body, in response to this.
  • 12/16/13 - Added link to cgminer mirror, thanks to scubasteve812 and thanks to Bagrisham.
  • 12/16/13 - Note about removing brackets in response to this.
  • 12/15/13 - Fixed hash rate as per this comment, thanks lleti
  • 12/15/13 - Added info for all other ways of getting money, except for trading (placeholder for now)
  • 12/15/13 - Added windows GPU mining instructions 12/15/13 - Added wallet instructions, list of how to get money
submitted by lego-banana to dogecoin [link] [comments]

IOC Wallet Adding Nodes 1337 Installing wallet and add nodes tutorial (details in description) BitconnectX addnode (BCCX node) Lindacoin - adding nodes to the wallet for connections Bitcoin Miner vs Full Node - Programmer explains

addnode¶. addnode "node" "command". Attempts to add or remove a node from the addnode list. Or try a connection to a node once. Nodes added using addnode (or -connect) are protected from DoS disconnection and are not required to be full nodes/support SegWit as other outbound peers are (though such peers will not be synced from). Take Bitcoin for example – you have two types of nodes. Full nodes which store a copy blockchain and thus guarantee the security and correctness of the data on the blockchain by validating data. The second type is a lightweight node – each user participating, who needs to connect to a full node in order to synchronize to the current state of the network and be able to participate. The ... On the Main tab, click Start Bitcoin on system login. Click the Ok button to save the new settings. The next time you login to your desktop, Bitcoin Core GUI should be automatically started as an icon in the tray. If Bitcoin Core GUI does not automatically start, you may need to add it to an .xinit or .xsession file as described here. Bitcoin Core versions prior to 0.8.0 also could send IP Transactions to these nodes. If you included your bitcoin address in the "message" field, you might have had your coins back. Tor network. To use Bitcoin-Qt over Tor hidden services, in a terminal/console enter: bitcoin-qt -proxy=127.0.0.1:9050 -onlynet=tor To use Bitcoin with one specific Tor node, run bitcoin-qt -proxy=127.0.0.1:9050 ... Map shows concentration of reachable Bitcoin nodes found in countries around the world. LIVE MAP × Global nodes distribution 10995 nodes as of 1603632185. 1. n/a (2857) 2. Germany (1862) 3. United States (1798) 4. France (556) 5. Netherlands (422) 6. Singapore (307) 7. Canada (302) 8. United Kingdom (283) 9. Russian Federation (233) 10. Japan (214) 11. China (188) 12. Switzerland (139) 13 ...

[index] [26457] [22618] [3737] [51322] [38635] [37166] [36343] [43861] [44239] [44194]

IOC Wallet Adding Nodes

What is a Bitcoin Node? - Step by Step Explanation - Duration: 5:47. Blockgeeks 11,080 views. 5:47. How to Buy Cryptocurrency for Beginners (UPDATED Ultimate Guide) - Duration: 33:53. ... create file bitconnectx.conf in C:\Users\your_compuer_name\AppData\Roaming\bitconnectx and add nodes: addnode=45.58.117.114:33089 addnode=93.244.222.22:33089... 1337 Installing wallet and add nodes tutorial (details in description) Graham Smith. Loading... Unsubscribe from Graham Smith? Cancel Unsubscribe. Working... Subscribe Subscribed Unsubscribe 76 ... Как безопасно получить Bitcoin Gold бесплатно из blockchain.info, Bitcoin core и т.д. - Duration: 8:41. HANDY TV 7,396 views 8:41 Produced by https://CryptoCousins.com: On this episode we install a Bitcoin Core Full Node. Watch as we figure out the process. Join Tony Cecala and Gary Lel...

#