Coinbase – Buy & Sell Bitcoin, Ethereum, and more with trust
Download - Bitcoin
Download - Bitcoin - Bitcoin Core :: Bitcoin
How to Run a Full Bitcoin Node: 10-Step Guide for ...
TiPS (FedoraCoin)
TiPS (a.k.a. FedoraCoin) is a new state of the art cryptocoin based on the [Tips Fedora meme](http://knowyourmeme.com/memes/tips-fedora). Our objective is to become the tipping currency of the internet. More information is available in the [BitcoinTalk thread](https://bitcointalk.org/index.php?topic=380466.0).
https://github.com/gridcoin-community/Gridcoin-Research/releases/tag/5.0.0.0 Finally! After over ten months of development and testing, "Fern" has arrived! This is a whopper. 240 pull requests merged. Essentially a complete rewrite that was started with the scraper (the "neural net" rewrite) in "Denise" has now been completed. Practically the ENTIRE Gridcoin specific codebase resting on top of the vanilla Bitcoin/Peercoin/Blackcoin vanilla PoS code has been rewritten. This removes the team requirement at last (see below), although there are many other important improvements besides that. Fern was a monumental undertaking. We had to encode all of the old rules active for the v10 block protocol in new code and ensure that the new code was 100% compatible. This had to be done in such a way as to clear out all of the old spaghetti and ring-fence it with tightly controlled class implementations. We then wrote an entirely new, simplified ruleset for research rewards and reengineered contracts (which includes beacon management, polls, and voting) using properly classed code. The fundamentals of Gridcoin with this release are now on a very sound and maintainable footing, and the developers believe the codebase as updated here will serve as the fundamental basis for Gridcoin's future roadmap. We have been testing this for MONTHS on testnet in various stages. The v10 (legacy) compatibility code has been running on testnet continuously as it was developed to ensure compatibility with existing nodes. During the last few months, we have done two private testnet forks and then the full public testnet testing for v11 code (the new protocol which is what Fern implements). The developers have also been running non-staking "sentinel" nodes on mainnet with this code to verify that the consensus rules are problem-free for the legacy compatibility code on the broader mainnet. We believe this amount of testing is going to result in a smooth rollout. Given the amount of changes in Fern, I am presenting TWO changelogs below. One is high level, which summarizes the most significant changes in the protocol. The second changelog is the detailed one in the usual format, and gives you an inkling of the size of this release.
Highlights
Protocol
Note that the protocol changes will not become active until we cross the hard-fork transition height to v11, which has been set at 2053000. Given current average block spacing, this should happen around October 4, about one month from now. Note that to get all of the beacons in the network on the new protocol, we are requiring ALL beacons to be validated. A two week (14 day) grace period is provided by the code, starting at the time of the transition height, for people currently holding a beacon to validate the beacon and prevent it from expiring. That means that EVERY CRUNCHER must advertise and validate their beacon AFTER the v11 transition (around Oct 4th) and BEFORE October 18th (or more precisely, 14 days from the actual date of the v11 transition). If you do not advertise and validate your beacon by this time, your beacon will expire and you will stop earning research rewards until you advertise and validate a new beacon. This process has been made much easier by a brand new beacon "wizard" that helps manage beacon advertisements and renewals. Once a beacon has been validated and is a v11 protocol beacon, the normal 180 day expiration rules apply. Note, however, that the 180 day expiration on research rewards has been removed with the Fern update. This means that while your beacon might expire after 180 days, your earned research rewards will be retained and can be claimed by advertising a beacon with the same CPID and going through the validation process again. In other words, you do not lose any earned research rewards if you do not stake a block within 180 days and keep your beacon up-to-date. The transition height is also when the team requirement will be relaxed for the network.
GUI
Besides the beacon wizard, there are a number of improvements to the GUI, including new UI transaction types (and icons) for staking the superblock, sidestake sends, beacon advertisement, voting, poll creation, and transactions with a message. The main screen has been revamped with a better summary section, and better status icons. Several changes under the hood have improved GUI performance. And finally, the diagnostics have been revamped.
Blockchain
The wallet sync speed has been DRASTICALLY improved. A decent machine with a good network connection should be able to sync the entire mainnet blockchain in less than 4 hours. A fast machine with a really fast network connection and a good SSD can do it in about 2.5 hours. One of our goals was to reduce or eliminate the reliance on snapshots for mainnet, and I think we have accomplished that goal with the new sync speed. We have also streamlined the in-memory structures for the blockchain which shaves some memory use. There are so many goodies here it is hard to summarize them all. I would like to thank all of the contributors to this release, but especially thank @cyrossignol, whose incredible contributions formed the backbone of this release. I would also like to pay special thanks to @barton2526, @caraka, and @Quezacoatl1, who tirelessly helped during the testing and polishing phase on testnet with testing and repeated builds for all architectures. The developers are proud to present this release to the community and we believe this represents the starting point for a true renaissance for Gridcoin!
Summary Changelog
Accrual
Changed
Most significantly, nodes calculate research rewards directly from the magnitudes in EACH superblock between stakes instead of using a two- or three- point average based on a CPID's current magnitude and the magnitude for the CPID when it last staked. For those long-timers in the community, this has been referred to as "Superblock Windows," and was first done in proof-of-concept form by @denravonska.
Network magnitude unit pinned to a static value of 0.25
Max research reward allowed per block raised to 16384 GRC (from 12750 GRC)
New CPIDs begin accruing research rewards from the first superblock that contains the CPID instead of from the time of the beacon advertisement
Removed
500 GRC research reward limit for a CPID's first stake
6-month expiration for unclaimed rewards
10-block spacing requirement between research reward claims
Rolling 5-day payment-per-day limit
Legacy tolerances for floating-point error and time drift
The need to include a valid copy of a CPID's magnitude in a claim
10-block emission adjustment interval for the magnitude unit
Beacons
Added
One-time beacon activation requires that participants temporarily change their usernames to a verification code at one whitelisted BOINC project
Verification codes of pending beacons expire after 3 days
Self-service beacon removal
Changed
Burn fee for beacon advertisement increased from 0.00001 GRC to 0.5 GRC
Rain addresses derived from beacon keys instead of a default wallet address
Beacon expiration determined as of the current block instead of the previous block
Removed
The ability for developers to remove beacons
The ability to sign research reward claims with non-current but unexpired beacons
Unaltered
As a reminder:
Beacons expire after 6 months pass (180 days)
Beacons can be renewed after 5 months pass (150 days)
Renewed beacons must be signed with the same key as the original beacon
Superblocks
Added
Magnitudes less than 1 include two fractional places
Magnitudes greater than or equal to 1 but less than 10 include one fractional place
Changed
A valid superblock must match a scraper convergence
Removed
Superblock popularity election mechanics
Voting
Added
Yes/no/abstain and single-choice response types (no user-facing support yet)
Changed
To create a poll, a maximum of 250 UTXOs for a single address must add up to 100000 GRC. These are selected from the largest downwards.
Burn fee for creating polls scaled by the number of UTXOs claimed
50 GRC for a poll contract
0.001 GRC per claimed UTXO
Burn fee for casting votes scaled by the number of UTXOs claimed
0.01 GRC for a vote contract
0.01 GRC to claim magnitude
0.01 GRC per claimed address
0.001 GRC per claimed UTXO
Maximum length of a poll title: 80 characters
Maximum length of a poll question: 100 characters
Maximum length of a poll discussion website URL: 100 characters
Maximum number of poll choices: 20
Maximum length of a poll choice label: 100 characters
Removed
Magnitude, CPID count, and participant count poll weight types
The ability for developers to remove polls and votes
Detailed Changelog
[5.0.0.0] 2020-09-03, mandatory, "Fern"
Added
Backport newer uint256 types from Bitcoin #1570 (@cyrossignol)
Implement project level rain for rainbymagnitude #1580 (@jamescowens)
Upgrade utilities (Update checker and snapshot downloadeapplication) #1576 (@iFoggz)
Provide fees collected in the block by the miner #1601 (@iFoggz)
Add support for generating legacy superblocks from scraper stats #1603 (@cyrossignol)
Port of the Bitcoin Logger to Gridcoin #1600 (@jamescowens)
Implement zapwallettxes #1605 (@jamescowens)
Implements a global event filter to suppress help question mark #1609 (@jamescowens)
Add next target difficulty to RPC output #1615 (@cyrossignol)
Add caching for block hashes to CBlock #1624 (@cyrossignol)
Make toolbars and tray icon red for testnet #1637 (@jamescowens)
Add an rpc call convergencereport #1643 (@jamescowens)
Implement newline filter on config file read in #1645 (@jamescowens)
Implement beacon status icon/button #1646 (@jamescowens)
Add gridcointestnet.png #1649 (@caraka)
Add precision to support magnitudes less than 1 #1651 (@cyrossignol)
Replace research accrual calculations with superblock snapshots #1657 (@cyrossignol)
Publish example gridcoinresearch.conf as a md document to the doc directory #1662 (@jamescowens)
Add options checkbox to disable transaction notifications #1666 (@jamescowens)
Add support for self-service beacon deletion #1695 (@cyrossignol)
Add support for type-specific contract fee amounts #1698 (@cyrossignol)
Add verifiedbeaconreport and pendingbeaconreport #1696 (@jamescowens)
Add preliminary testing option for block v11 height on testnet #1706 (@cyrossignol)
Add verified beacons manifest part to superblock validator #1711 (@cyrossignol)
Implement beacon, vote, and superblock display categories/icons in UI transaction model #1717 (@jamescowens)
PSA: Enable Tor as a simple way to make your node reachable.
Become one of the 10% of node operators that receive incoming connections. Installing bitcoin core is easy, and with pruning it really isn't the space sink it is characterized as. Even a modest computer can complete the initial block download (IBD) and become a full node. But what some users (90%) find a bit more challenging, is how to become a listening node. Listening nodes are an important part of the network, and are simple enough to enable. I can think of 4 ways to do it:
Operate on an OS and Network that support uPnP, allowing bitcoin to open the ports for you.
Subscribe to a VPN that allows you to open ports through their service.
Manually configure your OS and network to forward port 8333 and 18333.
Run Tor and direct bitcoin to listen through it.
I'll discuss #4. Obviously #1 or #2 are easier, but require a VPN subscription or uPnP enabled HW. And if you live in a dorm or don't control the network, Tor may be the only free option available. As a bit of background, bitcoin supports three networks that your node can listen on:
IPv4 - This is the "legacy" internet that most are used to
IPv6 - A not so new upgrade allowing trillions of addresses instead of billions
Tor) - A privacy network allowing encrypted traffic to remain anonymous
Obviously, the more you enable, the better, but here are the basic steps for Tor in broad strokes. If you have any questions post them here and I'll see if we can't help you out:
Record the hostname: type .\HiddenService\hostname as
Add the bitcoin.conf options suggested below
Restart the bitcoin-qt program
(Optional) Activate the bitnodes crawler at https://bitnodes.io/nodes/-8333/
It may take a while for your node to show up on bitnodes. I've found the check button sometimes has trouble with onions. Of course you don't need to do it, but it can provide a simple way to check status once your on the list.
torrc file: (replace c:\windows with the proper path as needed)
```
Change to C:\Windows\ServiceProfiles\LocalService\AppData\Roaming
Log notice file \tor\service.log
Bridges may be needed if the Gov't shuts down Tor exit nodes. Get Bridges by
emailing [email protected] from Gmail (only) and uncomment as follows:
Windows / Linux Guide to using Trezor with Bitcoin Core (HWI)
This is a guide to using your Trezor with Bitcoin Core. It may seem like more trouble than it's worth but many applications use Bitcoin Core as a wallet such as LND, EPS, and JoinMarket. Learning how to integrate your Trezor into a Bitcoin Core install is rather useful in many unexpected ways. I did this all through the QT interfaces, but it's simple to script. There is a much simpler guide available from the HWI github, and the smallest Linux TLDR is here Unfortunately, I don't have access to a Coldcard or Ledger. I'm not sure how the setpin or -stdinpass parameters are handled on that HW.
( A ) Install TrezorCTL, HWI, and build GUI
You only need to set the wallet up once, but may repeat to upgrade
( B ) Create a Trezor wallet in Bitcoin Core (testnet)
You only need to set the wallet up once, no private key data is stored, only xpub data
( B.I ) Retrieve keypool from HWI-QT
Launch hwi-qt.exe --testnet (assuming testnet)
Click Set passphrase (if needed) to cache your passphrase then click Refresh
Select you trezor from the list then click Set Pin (if needed)
Ensure your Trezor in the dropdown has a fingerprint
Select Change keypool options and choose P2WPKH
Copy all the text from the Keypool textbox
( B.II ) Create the wallet in Bitcoin QT
Launch Bitcoin Core (testnet) (non-pruned) 2
Select Console from the Window menu
Create a wallet createwallet "hwi" true
Ensure that hwi is selected in the console wallet dropdown
Verify walletname using the getwalletinfo command
Import keypool importmulti '' (note ' caging)
Rescan if TXNs are missing rescanblockchain 3
( C.I ) Grab Tesnet coins
Select the Receive tab in Bitcoin Core (testnet)
Ensure that the Wallet dropdown has hwi selected
Select Create new receiving address and copy address
Google "bitcoin testnet faucet" and visit a few sites
Answer captcha and input your addressed copied from C.I.3
( D ) Spending funds with HWI
This is how you can spend funds in your Trezor using Bitcoin Core (testnet)
( D.I ) Create an unsigned PSBT
Select the Send tab in Bitcoin Core (testnet)
Ensure that the Wallet dropdown has hwi selected
Verify your balance in Watch-only balance
Rescan if balance is wrong (see B.II.7) 3
Craft your TXN as usual, then click Create Unsigned
Copy the PSBT to your clipboard when prompted
( D.II ) Sign your PSBT
In HWI-QT click Sign PSBT
Paste what you copied in D.I.6 in PSBT to Sign field
Click Sign PSBT
Copy the text for PSBT Result
( D.III ) Broadcast your TXN
Select the Console window in Bitcoin Core (testnet)
Ensure that the Wallet dropdown has hwi selected
Finalize PSBT: finalizepsbt
Copy the signed TXN hex from the hex field returned
Broadcast TXN: sendrawtransaction
Final Thoughts
I did this all through the GUI interfaces for the benefit of the Windows users. Windows console is fine, but the quote escaping in windows console is nightmarish. Powershell would be good, but that throws this on a whole another level for most Windows folks. There is also the need to use HWI-QT due to a bug in blank passphrases on the commandline. You can work around it by toggling passphrase off or on, but again, it's more than I wanted to spell out. Footnotes:
1. - Later version of python put the activate script under 'bin' instead of 'Script'
2. - You can run pruned, but you need to have a fresh wallet
3. - Rescan is automatic on 'importmulti' but I was pruned so it was wierd
Windows Guide to using Trezor with Bitcoin Core (HWI)
This is a guide to using your Trezor with Bitcoin Core. It may seem like more trouble than it's worth but many applications use Bitcoin Core as a wallet such as LND, EPS, and JoinMarket. Learning how to integrate your Trezor into a Bitcoin Core install is rather useful in many unexpected ways. I did this all through the QT interfaces, but it's simple to script. There is a much simpler guide available from the HWI github, and the smallest TLDR is here
( A ) Install TrezorCTL, HWI, and build GUI
You only need to set the wallet up once, but may repeat to upgrade
( B ) Create a Trezor wallet in Bitcoin Core (testnet)
You only need to set the wallet up once, no private key data is stored, only xpub data
( B.I ) Retrieve keypool from HWI-QT
Launch hwi-qt.exe --testnet (assuming testnet)
Click Set passphrase (if needed) to cache your passphrase then click Refresh
Select you trezor from the list then click Set Pin (if needed)
Ensure your Trezor in the dropdown has a fingerprint
Select Change keypool options and choose P2WPKH
Copy all the text from the Keypool textbox
( B.II ) Create the wallet in Bitcoin QT
Launch Bitcoin Core (testnet) (non-pruned) 2
Select Console from the Window menu
Create a wallet createwallet "hwi" true
Ensure that hwi is selected in the console wallet dropdown
Verify walletname using the getwalletinfo command
Import keypool importmulti '' (note ' caging)
Rescan if TXNs are missing rescanblockchain 3
( C.I ) Grab Tesnet coins
Select the Receive tab in Bitcoin Core (testnet)
Ensure that the Wallet dropdown has hwi selected
Select Create new receiving address and copy address
Google "bitcoin testnet faucet" and visit a few sites
Answer captcha and input your addressed copied from C.I.3
( D ) Spending funds with HWI
This is how you can spend funds in your Trezor using Bitcoin Core (testnet)
( D.I ) Create an unsigned PSBT
Select the Send tab in Bitcoin Core (testnet)
Ensure that the Wallet dropdown has hwi selected
Verify your balance in Watch-only balance
Rescan if balance is wrong (see B.II.7) 3
Craft your TXN as usual, then click Create Unsigned
Copy the PSBT to your clipboard when prompted
( D.II ) Sign your PSBT
In HWI-QT click Sign PSBT
Paste what you copied in D.I.6 in PSBT to Sign field
Click Sign PSBT
Copy the text for PSBT Result
( D.III ) Broadcast your TXN
Select the Console window in Bitcoin Core (testnet)
Ensure that the Wallet dropdown has hwi selected
Finalize PSBT: finalizepsbt
Copy the signed TXN hex from the hex field returned
Broadcast TXN: sendrawtransaction
Final Thoughts
I did this all through the GUI interfaces for the benefit of the Windows users. Windows console is fine, but the quote escaping in windows console is nightmarish. Powershell would be good, but that throws this on a whole another level for most Windows folks. There is also the need to use HWI-QT due to a bug in blank passphrases on the commandline. You can work around it by toggling passphrase off or on, but again, it's more than I wanted to spell out. Footnotes:
1. - Later version of python put the activate script under 'bin' instead of 'Script'
2. - You can run pruned, but you need to have a fresh wallet
3. - Rescan is automatic on 'importmulti' but I was pruned so it was wierd
Subject: PSA: Make your node reachable by using Tor There is usually a post every few months with someone asking for tips on how to make their node reachable. It's always a hard question to answer since its impossible to know what type of routers and firewalls they are going to have to punch through. This is especially difficult in college dorms. One cheap (and easy) way around it is to to just jump through a few extra steps to make your bitcoin node a bitcoin onion node. Tor is great about traversing routers and firewalls like a hot knife through butter.
Forgot to upgrade your node? Here's how to get back onto the upgraded BCH network:
These instructions are for those who left old versions (0.20.12 or older) of Bitcoin ABC running through the May 15th, 2020 upgrade. Follow these instructions to get back on the main network. If you are using bitcoin-qt, follow these steps:
Stop your running node
Delete the list of nodes you have banned: rm ~/.bitcoin/banlist.dat
In the console type reconsiderblock 00000000000000000033dfef1fc2d6a5d5520b078c55193a9bf498c5b27530f7
Wait until your node is on the correct chain. This could take some time if your old node was running for a while, and other nodes banned you on the network. You can check that you are on the correct chain by typing getblockchaininfo and verifying the information with a public block explorer such as https://explorer.bitcoin.com/bch, https://blockchair.com/bitcoin-cash, or https://cash.coin.dance/.
If you are running bitcoind, follow these steps:
Stop your running node
Delete the list of nodes you have banned: rm ~/.bitcoin/banlist.dat
Use bitcoin-cli to type: ./bin/bitcoin-cli reconsiderblock 00000000000000000033dfef1fc2d6a5d5520b078c55193a9bf498c5b27530f7
Wait until your node is on the correct chain. This could take some time if your old node was running for a while, and other nodes banned you on the network. You can check that you are on the correct chain by typing ./bin/bitcoin-cli getblockchaininfo and verifying the information with a public block explorer such as https://explorer.bitcoin.com/bch, https://blockchair.com/bitcoin-cash, or https://cash.coin.dance/.
The last month in the world of Mousecoin has been HUGE! There have been many changes, the addition of new awesome ways to earn MIC3 including ourFaucetspage and thePhoneumGames. We have also seen the launch of ourCommunity Membership, which entitles each registered user to receive up to 200,000 MIC3 per month. We hope you are all keeping safe and are happy to provide you with our Mousecoin Network May 2020 Report.
MOUSECOIN IN GAMES!!
FINALLY, after months of negotiation and with the help ofPhoneum, Mousecoin has partnered withPhoneumto be included in two of the most popularPhoneumcrypto games currently available.We have added a newGamespage, whiche features all the information and link for the games, with more to come.Here is the run down:
Crypto Treasures
📷 📷
📷 Crypto Treasures is a game, where players complete various quests, trivia and mini games to unlock Gold (in-game currency), Treasure Chests, Items, Collectibles, and various Crypto currencies, including the featured Mousecoin (MIC3).
Crypto Planet
📷 📷
📷 Visit a new type of planet, one that allows you to earn real cryptocurrencies while playing a beautiful and futuristic game. The main objective is to extract the valuable resources of the planet: Crystals. There is a special machine designed specifically to dig up the Crystals automatically and deliver them to you. All you have to do is activate the Digger and after 4 hours, it will have the resources ready to be claimed.
COMMUNITY MEMBERSHIP
Earn up to 200,000 MIC3 Per Month!
At the beginning of last month we began establishing ourCommunity Membershipwhich offers all registered Mousecoin Members a share of the rewards earned from theCommunity Fundjust for being a member and following Mousecoin on all of oursocial media.As we come to the end of the first month we are currently in the process of checking all registrations and working out payments. We have also updated the profile page to include a Member News tab, Verified Notifications for each Social Media and a Monthly Payment History section. We are currently working on verifying all accounts registered before 1/6/2020, and should have all of these processed in the next few days, with all payment going out before the end of the week.
Become a part of the Mousecoin (MIC3) Community.Membership is FREE and it comes with HUGE bonuses!!
Just a reminder for the community and also for any new members, we have added aWallet Setup Guidespage, which takes any first time user of Mousecoin step-by-step through the process of installing their Mousecoin wallet and getting it online. The guide uses the latestblockchain snapshotfound on theWallet DownloadsPage in the example explanation meaning that all new members of the Mousecoin community will be able to get their wallets online faster as the sync time should be minimal. We will be updating theblockchain snapshotat least once every month to ensure that people have access to the most up to date blockchain info. The latestblockchain snapshotwas performed on the 1st June 2020. The wallet version is currenty V1.0.0.0, with future releases of the Mousecoin wallet coming soon If you are new to crypto currency or just after a bit of guidance setting up the Mousecoin wallet, check out ourWallet Setup Guides 📷Windows 📷Raspberry Pi 📷Wallet & Blockchain Snapshot Download (UPDATED 01-06-2020)
POS & STAKING
In the last month we asked the community if they would be interested in being a part of a Community Staking Pool. After investigations into this finding security flaws in most platforms, as well as the lack of interest from members of the community we have decided to not go ahead with the Community Staking Pool. While we understand that there are members of the Mousecoin Community that are unable to stake themselves for whatever reason, and that there are a number of staking platforms that offer pool staking for MIC3 to help these people stake, we will not officially be supporting any staking platforms.We ask all Community members using these or thinking about using these to keep in mind that any MIC3 hosted on these platforms is not in their wallets, and therefore not controlled by them. Do proper investigations into any platform that you use for this as there is always the possibility of loss. We encourage all members of the Mousecoin Community to stake from their own wallet (where possible) as this helps us to secure the network. If you need help setting up your wallet, go to ourWallet Setup Guidespage for step-by-step guides on setting up your Mousecoin wallet.
MOUSECOIN FAUCETS
We have updated the Mousecoin (MIC3)FaucetsPage: To make things clearer and we will be adding more faucets soon!
EXCHANGES
Last month we saw the edition of theUSDT/MIC3pair tonanu exchange. In our efforts to increase exposure of Mousecoin, we are still attempting to list on bothATAIXandUnnamed.Exhchange. ATAIXWe have risen to 18th position in the voting list onATAIX, but we still need your votes. Remember you can vote every 24 hours for this listing, and you can share in 125,000,000 MIC3 📷 Unnamed.ExhchangeThe exchange listing forUnnamed.Exhchangeis 0.05 BTC.For anyone unfamiliar with the exchange there are two ways that you can donate to the listing: 1. If you are already a member of, or wish to be a member ofUnnamed.Exhchange(and why wouldn’t you), you can put funds towards our listing by tipping us through the trollbox (Mousecoins). If you wish to be a member ofUnnamed.Exhchange, you can register here:https://www.unnamed.exchange/Login/Register 2. You can also donate to the listing fee through the following addresses:BTC – bc1qmaqzhfqcw0urva0rtgfz5qvq4rw7kdnp6j7754LTC – ltc1qc775eeftdde2jrevnyukrd2w9853jy5gmtv6rnDOGE – DEnBpriaFnKiNeBv6Q7MVxMg5hLv5urQFgUTIP – AUTyu2JhGAaCkM3KAmeBopto2bNBchNJfE If you would like to donate in another crypto available onUnnamed.Exhchange, we have opened up the chat on the Discord channelHEREto assist with this. Please request the address and we will provide it for you.ANY AND ALL DONATIONS ARE WELCOME!!This is a good exchange and getting a listing her should help lift the profile of MIC3. We will be reporting balances to the discord channelhttps://discord.gg/cYuA8FA
COMMUNITY FUND
📷 In the last month theCommunity Fundhas undergone a huge amount of change. We have completely moved all of our remaining balances away from 4Stake, with the MIC3 going to theCommunity FundMIC3 account and the remaining crypto’s towards out listing onUnnamed.Exhchange. TheCommunity Fundpage on the website has also been updated to reflect all of the changes.It is an exciting time for theCommunity Fundas we have now reached a balance that will sustain itself. This is why we have introduced the Community Member payment, and are able to sustain the faucets we have onhttps://erex.io/freecoin/and in thePhoneumGames. There is still more to come! 📷
Note: I don't know exactly how long it took because I didn't do it in one go. I guess it was like 4,5 days doing it only at night. At some points(2015Q3, 2018Q2) it slows down and ETA goes up to 16 weeks or something. The main bottleneck is IO. My 2013 mobile i3 has enough processing power to sync, I only used 3 threads and most of the time only one was close to 100%. The two directories that need to be written and read from intensively are chainstate and blocks/index. I pruned to 2GB and chainstate didn't go much over 3GB during the entire process. blocks/index is like 100MB. The best solution is to move chainstate and blocks/index to a ramdisk. If you don't have enough ram the linux kernel has a thing called zram. Zram creates a compressed swap(cache) file in ram, this effectively increases your ram size at the cost of a bit of processing power and access speed(of the compressed part). On my machine I can net a bit more than 1GB of extra ram. That's right, with linux you can download more ram! The second best solution is to leave chainstate and block/index on a sdd. From what I've tested it should take up between 5 whole days and 2 weeks. With regards to config, I didn't see much benefit in increasing the db cache over the default 450MB in bitcoin-qt. If I recall correctly, smaller prune sizes make chainstate larger. After the initial sync keeping up to date is very easy on resources. You can catch up a week in a few minutes. At the moment bitcoind is using 400MB but I'm still working on bringing that number down. Remember: If you want safety or if you want to help the network you need o run a full node. A full node is a node that verifies all transactions. A pruned node is a full node. Edit: bitocoind really likes to hover around 400MB, sometimes it gets higher than that, some times it get's lower. A lot of that is data, not code, so if you start running out of ram your OS should drop those pages and get down to 250~300MiB. If you really want the memory to be this low all the time, on linux, you can either: Use cgroups to set the swappiness of the process to 99 so all data gets swapped but not code does; Use systemd and set MemoryLimit=300MiB(for example) so almost all data gets swapped but no code. I don't think any of those options are worth the small setup hassle.
Reddcoin (RDD) Core Wallet v3.0.1 - January 09, 2020 Version 3.0.1 is the official release version of Reddcoin Core. It is available for download at Reddcoin Core's Github repository here: https://github.com/reddcoin-project/reddcoin/releases/tag/v3.0.1 This release features PoSV v2.supermajority activation and new staking ruleset (and minor misc fixes). v3.0.1 is still not yet MacOS Catalina compatible. We are still working and should have that fix issued very soon. Sincere apologies to our Mac-using ReddHeads. It is particularly important that all users upgrade, as once PoSV v2 is enforced, version 4 blocks will be rejected from the network entirely. Therefore v3.0.1 is a "strongly recommended" update for all users. Note: If you have already installed v3.0.0, this upgrade is not required. If you have not yet upgraded from v2.0.x or earlier, this is a REQUIRED upgrade. Please install the newest version v3.0.1 to avoid losing functionality during supermajority activation of PoSV v2. Reddcoin Core version 3.0.1 is now available from: https://github.com/reddcoin-project/reddcoin/releases Release Notes are available here and replicated below in this announcement: https://github.com/reddcoin-project/reddcoin/blob/mastedoc/release-notes.md This is a new major version release of Reddcoin. Previously, the original and subsequent versions of Reddcoin were taken from a fork of the Litecoin code base. With the release of Reddcoin V2.0.0, the code was based directly from a fork of Bitcoin. This allows for better source control and feature implementation from upstream changes into the future With the release of Reddcoin V3.0.0, the PoSV stake reward has been improved to allow for a target 5% network growth, in process re-incentivizing individual network stakers and providing for integrated dev support. Upgrading to this release is strongly recommended and required for continued operation. Once a supermajority of 90% is reached, old wallets will no longer accept the new v5 blocks. Please report bugs using the issue tracker at github: https://github.com/reddcoin-project/reddcoin/issues How to Upgrade If you are running an older version of Reddcoin, shut it down. Wait until it has completely shut down (which may take a few minutes for older versions). Run the installer (on Windows) or just copy over /Applications/Reddcoin-Qt (on Mac) or reddcoind/reddcoin-qt (on Linux). Start wallet. All done!
Reddcoin v3.0.0 introduced an updated PoSV method to better distribute staking rewards and target a overall 5% network growth. Staking and relay policy enhancements
To implement PoSV v2, Reddcoin Core's block templates are now for version 5 blocks only. When PoSV v2 consensus (Supermajority 9000/10000) is reached, only v5 blocks will be accepted by the network.This equates to approximately 90% of blocks being generated over 1 week period. Status at any time may be viewed in node debug.log Blockchain Download: Blockchain data for both testnet and mainnet along with instructions can be downloaded from github. https://github.com/reddcoin-project/bootstrap_files 3.0.1 changelog *83e212838 - John Nash, 2020-01-09 : really delete these files *3a1458ecd - Oliver Webb, 2020-01-08 : Added missing dependency libminiupnpc-dev for Jessie *d21915431 - Tiago Peralta, 2019-06-21 : Add vout to listtransactions/gettransaction *8d58ea7cf - Oliver Webb, 2020-01-08 : Script for downloading pre compiled binaries for Raspbian Jessie, Stretch or Buster *d4eced1bc - Oliver Webb, 2020-01-08 : Delete reddcoin_core_download_raspbian_stretch.sh *c5e9f91cf - Oliver Webb, 2020-01-08 : Delete reddcoin_core_download_raspbian_jessie.sh *5d5771b00 - Oliver Webb, 2020-01-08 : Delete reddcoin_core_download_raspbian_buster.sh *75c6ae91b - Oliver Webb, 2020-01-05 : add reddcoin-qt and remove starting daemon process *54c501787 - Oliver Webb, 2020-01-05 : add reddcoin-qt and remove starting daemon process *acb30a2b6 - Oliver Webb, 2020-01-05 : script files for Raspbian Jessie (also Stakebox) *cfddbe594 - John Nash, 2020-01-05 : Update copyright year and version *e46e5e7de - John Nash, 2020-01-05 : download script for pre compiled wallet *37386790a - John Nash, 2020-01-05 : change libssl deb packages links to github *9dbc772e6 - Oliver Webb, 2020-01-03 : download script for pre compiled wallet *857d697fd - Oliver Webb, 2020-01-03 : change libssl deb packages links to github *2cb74b9a8 - John Nash, 2019-12-31 : update copyright year *c641a1ab3 - Oliver Webb, 2019-12-30 : Raspberry Pi build script files for v3 wallet *a3f21a4a4 - John Nash, 2019-12-30 : add install script for building db4 update instructions for unix, osx, arm building using the db4 install script *5f6299b2a - John Nash, 2019-12-28 : docs: Update build notes for arm processors *465716c01 - John Nash, 2019-12-28 : test for arm devices *3fec3a535 - John Nash, 2018-02-02 : build: update source paths *5f6031ab4 - John Nash, 2019-12-28 : Scrypt n=1024 Pow hash based upon Colin Percival's Tarnsnap (2009) Modified by Artforz, coblee, pooler, wtogami, Nikolay Belikov, reddink *2fd4d91a0 - John Nash, 2019-12-24 : update copyright year *326828b36 - John Nash, 2019-12-24 : set release state true *8ebede0a6 - John Nash, 2019-12-24 : release notes *36df6fdfb - John Nash, 2019-12-23 : add check explictly for v5 blocks or greater *874dc1f0c - John Nash, 2019-12-17 : remove hardcoded global variable rearrange debug log output *763b25db8 - John Nash, 2019-12-17 : move copyright to new line *536baf635 - John Nash, 2019-12-17 : update version and set release state to false *cde9009f3 - John Nash, 2019-12-17 : update copyright year *ae41b7ed3 - John Nash, 2019-12-17 : set isSuperMajority to 90% for mainnet *e43e1c8ed - John Nash, 2019-12-10 : additional logging to verify isSuperMajority in the debug.log output *e31783cac - John Nash, 2019-12-05 : add/update public key for mainnet *405c6f002 - John Nash, 2019-12-05 : add log output for current inflation rate *9cc43c3f7 - John Nash, 2019-12-02 : determine calculated stake based on posv version *7baa3bf75 - John Nash, 2019-11-25 : check the posv transaction for correct pubkey *9ffa7ca38 - John Nash, 2019-11-21 : check for posv v1 or posv v2 blocks when calculating stake reward *39f7aad68 - John Nash, 2019-11-14 : add logging *0e283e6c3 - John Nash, 2019-11-13 : correct maths *74cbdeffd - John Nash, 2019-11-11 : use new posv v2 functions addidtional logging *35d7413b5 - John Nash, 2019-11-11 : add new proofofstakereward *3d917216c - John Nash, 2019-11-11 : get inflation adjustment *f63d17443 - John Nash, 2019-11-08 : add the developer output split fund output *ca263c9c9 - John Nash, 2019-11-05 : add dev key to chainparams *df6996ab0 - John Nash, 2019-11-05 : add block version checking *14b663479 - John Nash, 2019-11-05 : increase block version Credits Thanks to everyone who contributed to coding, testing and feedback for this release, notably:
Dear Groestlers, it goes without saying that 2020 has been a difficult time for millions of people worldwide. The groestlcoin team would like to take this opportunity to wish everyone our best to everyone coping with the direct and indirect effects of COVID-19. Let it bring out the best in us all and show that collectively, we can conquer anything. The centralised banks and our national governments are facing unprecedented times with interest rates worldwide dropping to record lows in places. Rest assured that this can only strengthen the fundamentals of all decentralised cryptocurrencies and the vision that was seeded with Satoshi's Bitcoin whitepaper over 10 years ago. Despite everything that has been thrown at us this year, the show must go on and the team will still progress and advance to continue the momentum that we have developed over the past 6 years. In addition to this, we'd like to remind you all that this is Groestlcoin's 6th Birthday release! In terms of price there have been some crazy highs and lows over the years (with highs of around $2.60 and lows of $0.000077!), but in terms of value– Groestlcoin just keeps getting more valuable! In these uncertain times, one thing remains clear – Groestlcoin will keep going and keep innovating regardless. On with what has been worked on and completed over the past few months.
UPDATED - Groestlcoin Core 2.18.2
This is a major release of Groestlcoin Core with many protocol level improvements and code optimizations, featuring the technical equivalent of Bitcoin v0.18.2 but with Groestlcoin-specific patches. On a general level, most of what is new is a new 'Groestlcoin-wallet' tool which is now distributed alongside Groestlcoin Core's other executables. NOTE: The 'Account' API has been removed from this version which was typically used in some tip bots. Please ensure you check the release notes from 2.17.2 for details on replacing this functionality.
Builds are now done through Gitian
Calls to getblocktemplate will fail if the segwit rule is not specified. Calling getblocktemplate without segwit specified is almost certainly a misconfiguration since doing so results in lower rewards for the miner. Failed calls will produce an error message describing how to enable the segwit rule.
A warning is printed if an unrecognized section name is used in the configuration file. Recognized sections are [test], [main], and [regtest].
Four new options are available for configuring the maximum number of messages that ZMQ will queue in memory (the "high water mark") before dropping additional messages. The default value is 1,000, the same as was used for previous releases.
The rpcallowip option can no longer be used to automatically listen on all network interfaces. Instead, the rpcbind parameter must be used to specify the IP addresses to listen on. Listening for RPC commands over a public network connection is insecure and should be disabled, so a warning is now printed if a user selects such a configuration. If you need to expose RPC in order to use a tool like Docker, ensure you only bind RPC to your localhost, e.g. docker run [...] -p 127.0.0.1:1441:1441 (this is an extra :1441 over the normal Docker port specification).
The rpcpassword option now causes a startup error if the password set in the configuration file contains a hash character (#), as it's ambiguous whether the hash character is meant for the password or as a comment.
The whitelistforcerelay option is used to relay transactions from whitelisted peers even when not accepted to the mempool. This option now defaults to being off, so that changes in policy and disconnect/ban behavior will not cause a node that is whitelisting another to be dropped by peers.
A new short about the JSON-RPC interface describes cases where the results of anRPC might contain inconsistencies between data sourced from differentsubsystems, such as wallet state and mempool state.
A new document introduces Groestlcoin Core's BIP174 interface, which is used to allow multiple programs to collaboratively work to create, sign, and broadcast new transactions. This is useful for offline (cold storage) wallets, multisig wallets, coinjoin implementations, and many other cases where two or more programs need to interact to generate a complete transaction.
The output script descriptor (https://github.com/groestlcoin/groestlcoin/blob/mastedoc/descriptors.md) documentation has been updated with information about new features in this still-developing language for describing the output scripts that a wallet or other program wants to receive notifications for, such as which addresses it wants to know received payments. The language is currently used in multiple new and updated RPCs described in these release notes and is expected to be adapted to other RPCs and to the underlying wallet structure.
A new --disable-bip70 option may be passed to ./configure to prevent Groestlcoin-Qt from being built with support for the BIP70 payment protocol or from linking libssl. As the payment protocol has exposed Groestlcoin Core to libssl vulnerabilities in the past, builders who don't need BIP70 support are encouraged to use this option to reduce their exposure to future vulnerabilities.
The minimum required version of Qt (when building the GUI) has been increased from 5.2 to 5.5.1 (the depends system provides 5.9.7)
getnodeaddresses returns peer addresses known to this node. It may be used to find nodes to connect to without using a DNS seeder.
listwalletdir returns a list of wallets in the wallet directory (either the default wallet directory or the directory configured bythe -walletdir parameter).
getrpcinfo returns runtime details of the RPC server. Currently, it returns an array of the currently active commands and how long they've been running.
deriveaddresses returns one or more addresses corresponding to an output descriptor.
getdescriptorinfo accepts a descriptor and returns information aboutit, including its computed checksum.
joinpsbts merges multiple distinct PSBTs into a single PSBT. The multiple PSBTs must have different inputs. The resulting PSBT will contain every input and output from all the PSBTs. Any signatures provided in any of the PSBTs will be dropped.
analyzepsbt examines a PSBT and provides information about what the PSBT contains and the next steps that need to be taken in order to complete the transaction. For each input of a PSBT, analyze psbt provides information about what information is missing for that input, including whether a UTXO needs to be provided, what pubkeys still need to be provided, which scripts need to be provided, and what signatures are still needed. Every input will also list which role is needed to complete that input, and analyzepsbt will also list the next role in general needed to complete the PSBT. analyzepsbt will also provide the estimated fee rate and estimated virtual size of the completed transaction if it has enough information to do so.
utxoupdatepsbt searches the set of Unspent Transaction Outputs (UTXOs) to find the outputs being spent by the partial transaction. PSBTs need to have the UTXOs being spent to be provided because the signing algorithm requires information from the UTXO being spent. For segwit inputs, only the UTXO itself is necessary. For non-segwit outputs, the entire previous transaction is needed so that signers can be sure that they are signing the correct thing. Unfortunately, because the UTXO set only contains UTXOs and not full transactions, utxoupdatepsbt will only add the UTXO for segwit inputs.
getpeerinfo now returns an additional minfeefilter field set to the peer's BIP133 fee filter. You can use this to detect that you have peers that are willing to accept transactions below the default minimum relay fee.
The mempool RPCs, such as getrawmempool with verbose=true, now return an additional "bip125-replaceable" value indicating whether thetransaction (or its unconfirmed ancestors) opts-in to asking nodes and miners to replace it with a higher-feerate transaction spending any of the same inputs.
settxfee previously silently ignored attempts to set the fee below the allowed minimums. It now prints a warning. The special value of"0" may still be used to request the minimum value.
getaddressinfo now provides an ischange field indicating whether the wallet used the address in a change output.
importmulti has been updated to support P2WSH, P2WPKH, P2SH-P2WPKH, and P2SH-P2WSH. Requests for P2WSH and P2SH-P2WSH accept an additional witnessscript parameter.
importmulti now returns an additional warnings field for each request with an array of strings explaining when fields are being ignored or are inconsistent, if there are any.
getaddressinfo now returns an additional solvable Boolean field when Groestlcoin Core knows enough about the address's scriptPubKey, optional redeemScript, and optional witnessScript for the wallet to be able to generate an unsigned input spending funds sent to that address.
The getaddressinfo, listunspent, and scantxoutset RPCs now return an additional desc field that contains an output descriptor containing all key paths and signing information for the address (except for the private key). The desc field is only returned for getaddressinfo and listunspent when the address is solvable.
importprivkey will preserve previously-set labels for addresses or public keys corresponding to the private key being imported. For example, if you imported a watch-only address with the label "coldwallet" in earlier releases of Groestlcoin Core, subsequently importing the private key would default to resetting the address's label to the default empty-string label (""). In this release, the previous label of "cold wallet" will be retained. If you optionally specify any label besides the default when calling importprivkey, the new label will be applied to the address.
getmininginfo now omits currentblockweight and currentblocktx when a block was never assembled via RPC on this node.
The getrawtransaction RPC & REST endpoints no longer check the unspent UTXO set for a transaction. The remaining behaviors are as follows:
If a blockhash is provided, check the corresponding block.
If no blockhash is provided, check the mempool.
If no blockhash is provided but txindex is enabled, also check txindex.
unloadwallet is now synchronous, meaning it will not return until the wallet is fully unloaded.
importmulti now supports importing of addresses from descriptors. A desc parameter can be provided instead of the "scriptPubKey" in are quest, as well as an optional range for ranged descriptors to specify the start and end of the range to import. Descriptors with key origin information imported through importmulti will have their key origin information stored in the wallet for use with creating PSBTs.
listunspent has been modified so that it also returns witnessScript, the witness script in the case of a P2WSH orP2SH-P2WSH output.
createwallet now has an optional blank argument that can be used to create a blank wallet. Blank wallets do not have any keys or HDseed. They cannot be opened in software older than 2.18.2. Once a blank wallet has a HD seed set (by using sethdseed) or private keys, scripts, addresses, and other watch only things have been imported, the wallet is no longer blank and can be opened in 2.17.2. Encrypting a blank wallet will also set a HD seed for it.
signrawtransaction is removed after being deprecated and hidden behind a special configuration option in version 2.17.2.
The 'account' API is removed after being deprecated in v2.17.2 The 'label' API was introduced in v2.17.2 as a replacement for accounts. See the release notes from v2.17.2 for a full description of the changes from the 'account' API to the 'label' API.
addwitnessaddress is removed after being deprecated in version 2.16.0.
generate is deprecated and will be fully removed in a subsequent major version. This RPC is only used for testing, but its implementation reached across multiple subsystems (wallet and mining), so it is being deprecated to simplify the wallet-node interface. Projects that are using generate for testing purposes should transition to using the generatetoaddress RPC, which does not require or use the wallet component. Calling generatetoaddress with an address returned by the getnewaddress RPC gives the same functionality as the old generate RPC. To continue using generate in this version, restart groestlcoind with the -deprecatedrpc=generate configuration option.
Be reminded that parts of the validateaddress command have been deprecated and moved to getaddressinfo. The following deprecated fields have moved to getaddressinfo: ismine, iswatchonly,script, hex, pubkeys, sigsrequired, pubkey, embedded,iscompressed, label, timestamp, hdkeypath, hdmasterkeyid.
The addresses field has been removed from the validateaddressand getaddressinfo RPC methods. This field was confusing since it referred to public keys using their P2PKH address. Clients should use the embedded.address field for P2SH or P2WSH wrapped addresses, and pubkeys for inspecting multisig participants.
A new /rest/blockhashbyheight/ endpoint is added for fetching the hash of the block in the current best blockchain based on its height (how many blocks it is after the Genesis Block).
A new Window menu is added alongside the existing File, Settings, and Help menus. Several items from the other menus that opened new windows have been moved to this new Window menu.
In the Send tab, the checkbox for "pay only the required fee" has been removed. Instead, the user can simply decrease the value in the Custom Fee rate field all the way down to the node's configured minimumrelay fee.
In the Overview tab, the watch-only balance will be the only balance shown if the wallet was created using the createwallet RPC and thedisable_private_keys parameter was set to true.
The launch-on-startup option is no longer available on macOS if compiled with macosx min version greater than 10.11 (useCXXFLAGS="-mmacosx-version-min=10.11" CFLAGS="-mmacosx-version-min=10.11" for setting the deployment sdkversion)
A new groestlcoin-wallet tool is now distributed alongside Groestlcoin Core's other executables. Without needing to use any RPCs, this tool can currently create a new wallet file or display some basic information about an existing wallet, such as whether the wallet is encrypted, whether it uses an HD seed, how many transactions it contains, and how many address book entries it has.
Since version 2.16.0, Groestlcoin Core's built-in wallet has defaulted to generating P2SH-wrapped segwit addresses when users want to receive payments. These addresses are backwards compatible with all widely used software. Starting with Groestlcoin Core 2.20.1 (expected about a year after 2.18.2), Groestlcoin Core will default to native segwitaddresses (bech32) that provide additional fee savings and other benefits. Currently, many wallets and services already support sending to bech32 addresses, and if the Groestlcoin Core project sees enough additional adoption, it will instead default to bech32 receiving addresses in Groestlcoin Core 2.19.1. P2SH-wrapped segwit addresses will continue to be provided if the user requests them in the GUI or by RPC, and anyone who doesn't want the update will be able to configure their default address type. (Similarly, pioneering users who want to change their default now may set the addresstype=bech32 configuration option in any Groestlcoin Core release from 2.16.0 up.)
BIP 61 reject messages are now deprecated. Reject messages have no use case on the P2P network and are only logged for debugging by most network nodes. Furthermore, they increase bandwidth and can be harmful for privacy and security. It has been possible to disable BIP 61 messages since v2.17.2 with the -enablebip61=0 option. BIP 61 messages will be disabled by default in a future version, before being removed entirely.
The submitblock RPC previously returned the reason a rejected block was invalid the first time it processed that block but returned a generic "duplicate" rejection message on subsequent occasions it processed the same block. It now always returns the fundamental reason for rejecting an invalid block and only returns "duplicate" for valid blocks it has already accepted.
A new submitheader RPC allows submitting block headers independently from their block. This is likely only useful for testing.
The signrawtransactionwithkey and signrawtransactionwithwallet RPCs have been modified so that they also optionally accept a witnessScript, the witness script in the case of a P2WSH orP2SH-P2WSH output. This is compatible with the change to listunspent.
For the walletprocesspsbt and walletcreatefundedpsbt RPCs, if thebip32derivs parameter is set to true but the key metadata for a public key has not been updated yet, then that key will have a derivation path as if it were just an independent key (i.e. no derivation path and its master fingerprint is itself).
The -usehd configuration option was removed in version 2.16.0 From that version onwards, all new wallets created are hierarchical deterministic wallets. This release makes specifying -usehd an invalid configuration option.
This release allows peers that your node automatically disconnected for misbehaviour (e.g. sending invalid data) to reconnect to your node if you have unused incoming connection slots. If your slots fill up, a misbehaving node will be disconnected to make room for nodes without a history of problems (unless the misbehaving node helps your node in some other way, such as by connecting to a part of the Internet from which you don't have many other peers). Previously, Groestlcoin Core banned the IP addresses of misbehaving peers for a period (default of 1 day); this was easily circumvented by attackers with multiple IP addresses. If you manually ban a peer, such as by using the setban RPC, all connections from that peer will still be rejected.
The key metadata will need to be upgraded the first time that the HDseed is available. For unencrypted wallets this will occur on wallet loading. For encrypted wallets this will occur the first time the wallet is unlocked.
Newly encrypted wallets will no longer require restarting the software. Instead such wallets will be completely unloaded and reloaded to achieve the same effect.
A sub-project of Bitcoin Core now provides Hardware Wallet Interaction (HWI) scripts that allow command-line users to use several popular hardware key management devices with Groestlcoin Core. See their project page for details.
This release changes the Random Number Generator (RNG) used from OpenSSL to Groestlcoin Core's own implementation, although entropy gathered by Groestlcoin Core is fed out to OpenSSL and then read back in when the program needs strong randomness. This moves Groestlcoin Core a little closer to no longer needing to depend on OpenSSL, a dependency that has caused security issues in the past. The new implementation gathers entropy from multiple sources, including from hardware supporting the rdseed CPU instruction.
On macOS, Groestlcoin Core now opts out of application CPU throttling ("app nap") during initial blockchain download, when catching up from over 100 blocks behind the current chain tip, or when reindexing chain data. This helps prevent these operations from taking an excessively long time because the operating system is attempting to conserve power.
How to Upgrade?
Windows If you are running an older version, shut it down. Wait until it has completely shut down (which might take a few minutes for older versions), then run the installer. OSX If you are running an older version, shut it down. Wait until it has completely shut down (which might take a few minutes for older versions), run the dmg and drag Groestlcoin Core to Applications. Ubuntu http://groestlcoin.org/forum/index.php?topic=441.0
ALL NEW - Groestlcoin Moonshine iOS/Android Wallet
Built with React Native, Moonshine utilizes Electrum-GRS's JSON-RPC methods to interact with the Groestlcoin network. GRS Moonshine's intended use is as a hot wallet. Meaning, your keys are only as safe as the device you install this wallet on. As with any hot wallet, please ensure that you keep only a small, responsible amount of Groestlcoin on it at any given time.
Features
Groestlcoin Mainnet & Testnet supported
Bech32 support
Multiple wallet support
Electrum - Support for both random and custom peers
Encrypted storage
Biometric + Pin authentication
Custom fee selection
Import mnemonic phrases via manual entry or scanning
RBF functionality
BIP39 Passphrase functionality
Support for Segwit-compatible & legacy addresses in settings
Support individual private key sweeping
UTXO blacklisting - Accessible via the Transaction Detail view, this allows users to blacklist any utxo that they do not wish to include in their list of available utxo's when sending transactions. Blacklisting a utxo excludes its amount from the wallet's total balance.
Ability to Sign & Verify Messages
Support BitID for password-free authentication
Coin Control - This can be accessed from the Send Transaction view and basically allows users to select from a list of available UTXO's to include in their transaction.
HODL GRS connects directly to the Groestlcoin network using SPV mode and doesn't rely on servers that can be hacked or disabled. HODL GRS utilizes AES hardware encryption, app sandboxing, and the latest security features to protect users from malware, browser security holes, and even physical theft. Private keys are stored only in the secure enclave of the user's phone, inaccessible to anyone other than the user. Simplicity and ease-of-use is the core design principle of HODL GRS. A simple recovery phrase (which we call a Backup Recovery Key) is all that is needed to restore the user's wallet if they ever lose or replace their device. HODL GRS is deterministic, which means the user's balance and transaction history can be recovered just from the backup recovery key.
Features
Simplified payment verification for fast mobile performance
Groestlcoin Seed Savior is a tool for recovering BIP39 seed phrases. This tool is meant to help users with recovering a slightly incorrect Groestlcoin mnemonic phrase (AKA backup or seed). You can enter an existing BIP39 mnemonic and get derived addresses in various formats. To find out if one of the suggested addresses is the right one, you can click on the suggested address to check the address' transaction history on a block explorer.
Features
If a word is wrong, the tool will try to suggest the closest option.
If a word is missing or unknown, please type "?" instead and the tool will find all relevant options.
NOTE: NVidia GPU or any CPU only. AMD graphics cards will not work with this address generator. VanitySearch is a command-line Segwit-capable vanity Groestlcoin address generator. Add unique flair when you tell people to send Groestlcoin. Alternatively, VanitySearch can be used to generate random addresses offline. If you're tired of the random, cryptic addresses generated by regular groestlcoin clients, then VanitySearch is the right choice for you to create a more personalized address. VanitySearch is a groestlcoin address prefix finder. If you want to generate safe private keys, use the -s option to enter your passphrase which will be used for generating a base key as for BIP38 standard (VanitySearch.exe -s "My PassPhrase" FXPref). You can also use VanitySearch.exe -ps "My PassPhrase" which will add a crypto secure seed to your passphrase. VanitySearch may not compute a good grid size for your GPU, so try different values using -g option in order to get the best performances. If you want to use GPUs and CPUs together, you may have best performances by keeping one CPU core for handling GPU(s)/CPU exchanges (use -t option to set the number of CPU threads).
Features
Fixed size arithmetic
Fast Modular Inversion (Delayed Right Shift 62 bits)
SecpK1 Fast modular multiplication (2 steps folding 512bits to 256bits using 64 bits digits)
Use some properties of elliptic curve to generate more keys
SSE Secure Hash Algorithm SHA256 and RIPEMD160 (CPU)
Groestlcoin EasyVanity 2020 is a windows app built from the ground-up and makes it easier than ever before to create your very own bespoke bech32 address(es) when whilst not connected to the internet. If you're tired of the random, cryptic bech32 addresses generated by regular Groestlcoin clients, then Groestlcoin EasyVanity2020 is the right choice for you to create a more personalised bech32 address. This 2020 version uses the new VanitySearch to generate not only legacy addresses (F prefix) but also Bech32 addresses (grs1 prefix).
Features
Ability to continue finding keys after first one is found
Includes warning on start-up if connected to the internet
Ability to output keys to a text file (And shows button to open that directory)
Show and hide the private key with a simple toggle switch
Show full output of commands
Ability to choose between Processor (CPU) and Graphics Card (GPU) ( NVidia ONLY! )
Features both a Light and Dark Material Design-Style Themes
Free software - MIT. Anyone can audit the code.
Written in C# - The code is short, and easy to review.
Groestlcoin WPF is an alternative full node client with optional lightweight 'thin-client' mode based on WPF. Windows Presentation Foundation (WPF) is one of Microsoft's latest approaches to a GUI framework, used with the .NET framework. Its main advantages over the original Groestlcoin client include support for exporting blockchain.dat and including a lite wallet mode. This wallet was previously deprecated but has been brought back to life with modern standards.
Features
Works via TOR or SOCKS5 proxy
Can use bootstrap.dat format as blockchain database
Import/Export blockchain to/from bootstrap.dat
Import wallet.dat from Groestlcoin-qt wallet
Export wallet to wallet.dat
Use both groestlcoin-wpf and groestlcoin-qt with the same addresses in parallel. When you send money from one program, the transaction will automatically be visible on the other wallet.
Rescan blockchain with a simple mouse click
Works as a full node and listens to port 1331 (listening port can be changed)
Fast Block verifying, parallel processing on multi-core CPUs
Mine Groestlcoins with your CPU by a simple mouse click
All private keys are kept encrypted on your local machine (or on a USB stick)
Lite - Has a lightweight "thin client" mode which does not require a new user to download the entire Groestlcoin chain and store it
Free and decentralised - Open Source under GNU license
Remastered Improvements
Bech32 support
P2sh support
Fixed Import/Export to wallet.dat
Testnet Support
Rescan wallet option
Change wallet password option
Address type and Change type options through *.conf file
Import from bootstrap.dat - It is a flat, binary file containing Groestlcoin blockchain data, from the genesis block through a recent height. All versions automatically validate and import the file "grs.bootstrap.dat" in the GRS directory. Grs.bootstrap.dat is compatible with Qt wallet. GroestlCoin-Qt can load from it.
In Full mode file %APPDATA%\Groestlcoin-WPF\GRS\GRS.bootstrap.dat is full blockchain in standard bootstrap.dat format and can be used with other clients.
Groestlcoin BIP39 Key Tool is a GUI interface for generating Groestlcoin public and private keys. It is a standalone tool which can be used offline.
Features
Selection options for 3-24 words (simply putting the space separated words in the first word box will also work) along with a bip39 passphrase
User input for total number of addresses desired
Creation of P2PKH, P2SH, P2WPKH and P2WSH addresses along with xpriv and xpub as per BIP32 spec, using a word list as the starting point following the BIP39 standard.
Pre-sets for BIP44, BIP49, BIP84 and BIP141 standards, along with custom user input for derivation path
Option for Hardened or non-hardened addresses
Option for Testnet private and public keys
Output containing derivation path, private key in WIF, integer and hex format, public key address, public point on curve and scriptpubkey
Results are output in a file titled 'wallet.txt' with the time addresses were generated, along with all information presented onscreen
Groestlcoin Electrum Personal Server aims to make using Electrum Groestlcoin wallet more secure and more private. It makes it easy to connect your Electrum-GRS wallet to your own full node. It is an implementation of the Electrum-grs server protocol which fulfils the specific need of using the Electrum-grs wallet backed by a full node, but without the heavyweight server backend, for a single user. It allows the user to benefit from all Groestlcoin Core's resource-saving features like pruning, blocks only and disabled txindex. All Electrum-GRS's feature-richness like hardware wallet integration, multi-signature wallets, offline signing, seed recovery phrases, coin control and so on can still be used, but connected only to the user's own full node. Full node wallets are important in Groestlcoin because they are a big part of what makes the system be trust-less. No longer do people have to trust a financial institution like a bank or PayPal, they can run software on their own computers. If Groestlcoin is digital gold, then a full node wallet is your own personal goldsmith who checks for you that received payments are genuine. Full node wallets are also important for privacy. Using Electrum-GRS under default configuration requires it to send (hashes of) all your Groestlcoin addresses to some server. That server can then easily spy on your transactions. Full node wallets like Groestlcoin Electrum Personal Server would download the entire blockchain and scan it for the user's own addresses, and therefore don't reveal to anyone else which Groestlcoin addresses they are interested in. Groestlcoin Electrum Personal Server can also broadcast transactions through Tor which improves privacy by resisting traffic analysis for broadcasted transactions which can link the IP address of the user to the transaction. If enabled this would happen transparently whenever the user simply clicks "Send" on a transaction in Electrum-grs wallet. Note: Currently Groestlcoin Electrum Personal Server can only accept one connection at a time.
Features
Use your own node
Tor support
Uses less CPU and RAM than ElectrumX
Used intermittently rather than needing to be always-on
Doesn't require an index of every Groestlcoin address ever used like on ElectrumX
UPDATED – Android Wallet 7.38.1 - Main Net + Test Net
The app allows you to send and receive Groestlcoin on your device using QR codes and URI links. When using this app, please back up your wallet and email them to yourself! This will save your wallet in a password protected file. Then your coins can be retrieved even if you lose your phone.
Changes
Add confidence messages, helping users to understand the confidence state of their payments.
Handle edge case when restoring via an external app.
Count devices with a memory class of 128 MB as low ram.
Introduce dark mode on Android 10 devices.
Reduce memory usage of PIN-protected wallets.
Tapping on the app's version will reveal a checksum of the APK that was installed.
Fix issue with confirmation of transactions that empty your wallet.
Groestlcoin Sentinel is a great solution for anyone who wants the convenience and utility of a hot wallet for receiving payments directly into their cold storage (or hardware wallets). Sentinel accepts XPUB's, YPUB'S, ZPUB's and individual Groestlcoin address. Once added you will be able to view balances, view transactions, and (in the case of XPUB's, YPUB's and ZPUB's) deterministically generate addresses for that wallet. Groestlcoin Sentinel is a fork of Groestlcoin Samourai Wallet with all spending and transaction building code removed.
On all the tutorials I see for running bitcoin on a raspberry pi, they all git clone bitcoin from github and build bitcoind from source. Is this necessary? Can I not just download / verify signatures of bitcoind / bitcoin-qt from bitcoin.org and run the executables?
How will the (literally) growing problem of an enormous blockchain be addressed in the future?
To my knowledge, we need a complete history of the blockchain to be able to assure ourselves that transactions and balances are accurate. Could 'someone' we trust cryptographically sign and verify a block in the middle of the chain? For instance, Mt. Gox could take block 210,000 and a snapshot of all known balances, and sign it with the private key and certificate they use for the website. How do bitcoin wallets run on cell phones without a complete copy of the multi-gigabyte blackchain? I quess my beef is that when I recently installed bitcoin-qt on a new computer, it took me like 2 days to download the history to be able to use my new wallet freely... Is this making any sense?
The reason for the update My Reddcoin Core software crashed and became unusable. My Raspberry Pi 3B would lag and freeze, I couldn't stake anymore.
Instead of just redoing everything the same way, I wanted to see if I could improve on 3 points:
Use an OS that was lighter
Update the Reddcoin Core software (2.0.0.0 => 2.0.1.2)
Make improvements to the configuration.
The updates
OS: using Lubuntu instead of Ubuntu MATE. Lubuntu uses less resources (130 MB RAM vs. 190 MB RAM on initial boot).
Reddcoin Core: v2.0.1.2-a8767ba-beta instead of v2.0.0.0-92768f9-beta.
Swap: using a swap partiton instead of a swap file. Also adjusting the swap size: from 1 GB to 2 GB, after reading the comments to my previous tutorial.
All data to USB: Blockchain data and the swap are now stored on the USB drive, instead of the SD card.
Private keys: added instructions on how to backup the private keys of your Reddcoin addresses!
If you would like to tip me Writing a tutorial like this takes time and effort; tips are appreciated. My Reddcoin address: RqvdnNX5MTam855Y2Vudv7yVgtXdcYaQAW.
Storage space: I am using an 8 GB microSD card for the OS, and a 128 GB USB drive for data. Minimums I would recommend: 8GB SD card and 32 GB USB drive.
Reddcoin Core client version: v2.0.1.2-a8767ba-beta (most recent version at this moment). ↳ Screenshot
Steps
You need the OS; Lubuntu. Download Lubuntu (707 MB) for the Raspberry Pi: https://ubuntu-pi-flavour-maker.org/download/. It's a .torrent download, so you will need a BitTorrent client. Message me or post in this thread if you need help with this.
You need software to write the OS to the SD card. I use Etcher. Download Etcher: https://etcher.io/.
Run Etcher.
Select image: select the lubuntu-16.04.2-desktop-armhf-raspberry-pi.img.xz file.
Select drive: select your microSD card.
Flash.
Plug the SD card into your Raspberry Pi and power it up.
Lubuntu should boot up.
Set up Lubuntu, connect to the internet (wired or wireless). ↳ As username, I chose "rpi3b". You will see this username throughout this whole tutorial.
Make sure date and time are correct ([Menu] > System Tools > Time and Date). ↳ Click on Unlock to make changes. I personally change Configuration to "Keep synchronized with Internet servers". ↳ Screenshot
Reboot ([Menu] > Logout > Reboot). I am connected to wifi, but have issues getting wifi to work on initial boot. A reboot solves this issue.
Make sure system is up-to-date, install never versions.
Open LXTerminal ([Menu] > System Tools > LXTerminal). ↳ Screenshot
Enter the following in LXTerminal: sudo apt update && sudo apt upgrade ↳ Screenshot
You will be asked if you really want to continue. Enter Y (yes).
Updates are being installed! Wait until it's finished.
Install programs that will be used in this tutorial.
GParted: to partition the USB drive.
Htop: to see the amount of memory (RAM) and swap that is in use.
Enter the following in LXTerminal to install these 2 programs. sudo apt install gparted && sudo apt install htop ↳ Screenshot
Create 2 partitions on the USB drive: 1) Swap partition 2) data partition (for the Reddcoin blockchain) The swap partition is necessary: The Reddcoin wallet can be memory intensive. To prevent any crashes or freezes, add 2 GB of 'virtual' memory by creating a swap partition.
Important: Backup your USB drive if needed. The USB drive will be formatted, so the data on the USB drive will be wiped.
Please use the USB drive solely for this purpose, do not combine it with other stuff.
Keep your USB drive plugged in, do not (randomly) plug it out.
Plug your USB drive in.
GParted will be used to create the partititons. Start GParted via LXTerminal: sudo gparted ↳ Screenshot
In GParted, switch from your SD card (default) to your USB drive. ↳ Screenshot ↳ Screenshot
You will now see the all the partition on USB drive. Delete every partition (right mouse click). If you can't select Delete, do an Unmount first. ↳ Screenshot ↳ Screenshot
After deleting all partition, you will only see 'unallocated' space on your USB drive. ↳ Screenshot
Create the first partition: the swap partition. Right click on the blank space, select New and enter the following:
Apply the changes. Click on the check mark or select Edit > Apply All Operations. ↳ Screenshot ↳ Screenshot
Important: The name of the swap partition is needed later, so please write it down. Mine is /dev/sda1 (first partition on first drive (drive 'a')). ↳ Screenshot
Reboot. After the reboot, the data partition you just created should be visible on your desktop. ↳ Screenshot
The swap partition is created, so now we can enable and use it.
The swap in use can be monitored with the program Htop. Open Htop ([Menu] > System Tools > Htop) to see the 'Swp' (swap) in use. ↳ Screenshot By default, swap is not used, so 0K. ↳ Screenshot You can leave Htop open.
To enable the swap partition, open LXTerminal and enter the following commands: (Assuming /dev/sda1 is your swap partition.)
You've enabled the swap partition. Switch back to Htop and check the 'Swp' (swap) value. It should read '2.0G'. ↳ Screenshot
To make sure the swap file is persistent (so it survives a reboot), you have to add a line to the /etc/fstab file.
In LXTerminal, enter the following command to open the file in Leafpad (text editor): sudo leafpad /etc/fstab ↳ Screenshot
In Leafpad, add this text in a new line: /dev/sda1 swap swap defaults 0 0 ↳ Screenshot (I've added spaces to vertically align the text.)
Save and close the file.
Reboot your Pi.
To see if the swap partition is in use after a reboot, open Htop ([Menu] > System Tools > htop) and check the 'Swp' (swap) value. It should read '2.0G'. ↳ Screenshot
So, the swap partition is enabled and in use, and the data partition is prepared. We now can install the necessary software for the Reddcoin wallet; enter the following commands into LXTerminal:
After the reboot, open LXTerminal again. Download, unpack, configure, build and install Berkeley DB.
Set the working directory to your USB drive: cd /media/rpi3b/usb (rpi3b is the username I chose; if you have a different username, change it to yours.) ↳ Screenshot
Download the source of the Reddcoin wallet and build it.
Set the working directory to your USB drive: cd /media/rpi3b/usb (rpi3b is the username I chose; if you have a different username, change it to yours.)
Speed up synchronizing with the Reddcoin blockchain by bootstrapping.
Set the working directory to your USB drive: cd /media/rpi3b/usb (rpi3b is the username I chose; if you have a different username, change it to yours.)
Unpack the file (large file, takes around 15 minutes to unpack): sudo xz -d bootstrap.dat.xz ↳ Screenshot
After a successful unpack, your will find the file bootstrap.dat in your USB root folder. ↳ Screenshot
On the first run of the Reddcoin Core client, it will ask for a data directory to store the blockchain and wallet data.
Start the Reddcoin Core client: sudo /media/rpi3b/usb/reddcoin/src/qt/reddcoin-qt ↳ Screenshot
The welcome screen will appear and ask you about the data directory. I suggest a new folder on your USB drive, I picked blockchain. The directory will be created with all the necessary files. ↳ Screenshot
Click on the three dots (...) on the right. ↳ Screenshot
Click on Create Folder at the upper right corner. Type and enter in the folder name. (In my case: blockchain.) Click on Open. ↳ Screenshot ↳ Screenshot ↳ Screenshot
After selecting the directory, the Reddcoin Core client will start. Wait till it's fully loaded and close it.
Move the bootstrap.dat file to your data directory you selected in the previous step. By doing this, Reddcoin Core will use the bootstrap.dat file to import the blockchain, which speeds up syncing. sudo mv bootstrap.dat /media/rpi3b/usb/blockchain/ (Assuming blockchain as data directory.) ↳ Screenshot
The Reddcoin Core client set up is completed, but you still have to sync fully with the blockchain before you can send, receive and stake.
Keep the client running until it's fully synchronized. It will use the bootstrap file first, and download the rest of the blockchain to complete the sync. This can take some time (it took 2 days for me). Syncing the blockchain uses a lot of resources, so the software may react slow.
You can see the progress in the debug window (Help > Debug window). ↳ Screenshot
When the synchronization is completed, the red (out of sync) will disappear on the Overview screen! ↳ Screenshot
When synchronization is complete, you can start staking your Reddcoins.
Your wallet will be encrypted, and the Reddcoin Core client will be closed. Launch the Reddcore Client again. sudo /media/usb/reddcoin/src/qt/reddcoin-qt
To start stake, you need to unlock your wallet (by entering your password).
[01:11] Reddcoin Core started (sudo password entered).
[01:13] Message shown on screen: Loading block index...
[10:14] Message shown on screen: Verifying blocks...
[10:18] Message shown on screen: Loading wallet...
[12:49] Message shown on screen: Done loading
[13:13] Reddcoin Core ready to use.
Extra
Backup Backup your wallet to prevent losing the RDDs in your wallet! There are two methods to backup, do both. Make new backups if you create a new receiving address!
Method 1: Backup your wallet.dat. Open Reddcoin Core. Use the menu to backup: File > Backup Wallet... ↳ Screenshot
Method 2: Backup your private keys. In case you lose your wallet.dat backup, you still can import your private keys later when needed.
To extract your private keys:
If you have a passphrase on your wallet, unlock your wallet first. Settings -> Unlock Wallet... (make sure 'For staking only' is not checked) ↳ Screenshot ↳ Screenshot
You can write down your private key or copy and save it in a document. Make sure you save it somewhere only you can access it.
To import later: Debug window -> Console -> importprivkey [label] [label] is optional. ↳ Screenshot (without a label) ↳ Screenshot (with a label)
Boot with only 1 USB drive plugged in: Make sure only the USB drive (with the swap partition and data partition) is plugged in when you boot up your Raspberry Pi. This to make sure the swap partition (/dev/sda1) is recognized correctly. If you boot up with multiple USB drives, Lubuntu might see the USB drive with the swap partition as the second drive (instead of the first drive), and ignore the 2 GB swap partition. If this happens, starting Reddcoin can render the Raspberry Pi unresponsive.
Connection issues If you have issues syncing the blockchain because you have 0 network connections, please follow the instructions in this thread.
Start Reddcoin Core easier Run a shell script (.sh file), so you can start Reddcoin just by double clicking on an icon on your Desktop.
Right Click on your Desktop and select Create New -> Empty File. ↳ Screenshot
Enter a file name, make sure it ends with .sh, and click on OK. I've chosen for Reddcoin.sh. ↳ Screenshot The file will be created on your Desktop. ↳ Screenshot
Add the command to start Reddcoin to the file.
Right click on the file, select Leafpad (to open the file in a text editor). ↳ Screenshot
Add the following to the file and save the file: sudo /media/rpi3b/usb/reddcoin/src/qt/reddcoin-qt ↳ Screenshot
To be able to execute the shell script (.sh), it has to have 'execute permissions'.
Right click on the file, and select Properties. ↳ Screenshot
Click on the Permissions tab.
For Execute, select Anyone, and click on OK. ↳ Screenshot
To start Reddcoin Core, double click on the file. A new window will pop-up, asking you what you want. Execute in Terminal is what we want, so you can click on enter. ↳ Screenshot Reddcoin Core will now start. Do not close the Terminal window, you can minimize it if needed.
Minimization options Adjust minimization options, so you can safely press on the X button (the close/exit button on the upper right corner).
Activate 'Minimize on close'. Settings -> Options... -> Window (tab) -> Minimize on close. ↳ Screenshot Reddcoin will still run when you click on the X button. To close/exit Reddcoin, right click on the Reddcoin icon in the system tray (bottom right corner). ↳ Screenshot
RealVNC VNC Viewer (client) and VNC Connect (server): To remote connect to the Raspberry Pi, I use VNC Viewer ad VNC Connect from RealVNC.
After your download is finished, open the file and click Install Package. ↳ Screenshot
To run the VNC Connect once:
Open [Menu] > Run, and enter: vncserver-x11 ↳ Screenshot
To auto run on startup:
Open Default applications for LXSession ([Menu] > Preferences > Default applications for LXSession). ↳ Screenshot
In LXSessions configuration, select Autostart in the menu left.
Under Manual autostarted applications, enter vncserver-x11 and click on + Add. ↳ Screenshot ↳ Screenshot
Reboot your Raspberry Pi and check if VNC Connect is started automatically after the reboot.
When VNC Connect is running, you'll see a VNC icon on the right bottom corner. Double click the icon to open VNC Connect and to see the IP address you need to enter to connect to your Raspberry Pi. ↳ Screenshot
Chromium as browser: The updates break Firefox, the browser crashes when you try to run it. Install another browser, Chromium, to solve this issue.
In LXTerminal, enter: sudo apt install chromium-browser ↳ Screenshot
You can run Chromium via [Menu] > Internet -> Chromium Web Browser ↳ Screenshot
Updates / Upgrades If Software Updater shows up and tells you that there is updated software available, do not install the updates using Software Updater. Use LXTerminal to update Lubuntu.
Open LXTerminal and enter this command to update: sudo apt update && sudo apt upgrade ↳ Screenshot
Credits:
cryptoBUZE on reddit.com; for getting the official arm_support_v2.zip to work.
worstkaas on reddit.com; for his suggestion of using 2 GB instead of 1 GB for the swap space.
Credits in previous tutorial:
My main source: damsal01 on reddcointalk.org. His RDD address for donation: Rqd8xDv6oV9BYFaVrLdkWcR5JU6sPPZTKs.
hieplenet on reddit.com. His RDD address for donation: RaF3TeWqgTzAdnaZQffnsxS74dag13zsAY.
joroob on Github.com. He made some adjustments to the reddcoin wallet source code so it will compile on ARM cpus. His RDD address for donation: Rb8754QZvpbw6DjrMV1qX9SnHzYnSyXRMC.
Because cold wallets, such as those stored offline in a text file as I keep recommending in my standard advice below: All you need is a text file to put your wallets in, like this example from https://walletgenerator.net/?currency=Dogecoin 1,"D7WBUpdgLRtG6WyPsqjhaKiJR65X8ZGnkZ","6KieLMW1poAzNVnmLuQZqA262gxEQ51eLGdDK8e2GL2B4LHCKKb"2,"DM8LT16d49zHr8ByXbUwZb9UBXDGMaZRdc","6Ktgxdv6vN9v2bDHwcJBBb3oMRAgXJumESzBnxaXUSGFZoq6pWQ"3,"D5UCa51AfxjtVHQ46oYXe2YfkctTeLXPhx","6L2WSPWadRYCwt2L1CxH6zC7PoTYY3KyjxdiUoCqi5eyq6hQKvj" Use https://coinb.in/#settings to move coins. Download both sites and run them offline. Use https://bitinfocharts.com/dogecoin/ to check balances and transactions. See http://www.mocacinno.com/blog/create-sign-broadcast-transactions-using-coinb/ for coinb.in tutorial. And read the ELI5s (and my history) for more info. Are without doubt THE SAFEST way to store your coins. Plus, they consume no resources. No bandwidth, no network stress for every node we have, no storage of 20Gb+ blockchains, no weeks of waiting for things to sync, no tearing your hair out and posting desperate pleas for help, and most importantly, no coins irretrievably lost because you or your client screwed up.
What?
Wallets, ALL WALLETS are nothing but numbers. Very large numbers, but fundamentally no different from “7”, “42”, “911” or a phone number. They cannot be created nor destroyed, and you either know them or you don’t. Anyone who knows a key can use it to spend any coins it controls. Anyone who doesn’t know it, can’t. Don’t be the guy who doesn’t know his own keys. Keep them safe. Make copies. Keep those safe. Don’t let your friends, kid brother or random burglar find them, but don’t lose them either. The only other thing you need for a fully functional wallet is a way to spend coins. Coinb.in is such a way. There are others, such as DogeCoinMultiSig.org which tomcarbon built. Oh, and you can and should download it and run it locally.
Where?
The default entry point for coinb.in is https://coinb.in/#settings because this settings page is very well hidden. Its in the tiny gear wheel on the Broadcast page. Looking across the top of the page, you can see
+ New
Verify
Sign
Broadcast
Wallet
About
We’re only going to use three of these. New, Sign, Broadcast. Now, keep in mind that coinb.in is an old Bitcoin tool which tomcarbon added Dogecoin to. Sometimes it thinks its dealing with Bitcoin still, so if you see anything odd, go and make sure you’ve selected Dogecoin in the Settings page.
When?
This tool should be the only place you spend coins. Sure, some clients may look more convenient, but they all suffer from a very big coin-losing flaw. Whenever you split a UTXO, they create a new wallet to send the change to. And they DON’T TELL YOU! This means unless you back up after every transaction, you run a high risk of finding all your coins have ‘disappeared’ from your wallet, and you don’t recognise where they went. So if you use a client for the convenience as well as a text list of your wallets, you won’t know to add a new wallet to your masterfile. Its best to ditch the clients entirely.
How?
Now we come to the nitty-gritty. Lets use those three wallets above and assume that #1 is the source, #2 the destination and #3 the change wallet. Note that these won’t actually work, as none of them have ever been used, but they will do as examples. New Transaction Located at the bottom of the New menu, this will give you a page to enter your wallets and amounts. In the top field, you enter your source address or Key. If you use the key, it will calculate the address when you click the Load button, which should match what you expected. Note that Load only brings in the first 100 UTXOs. This is so that you can retrieve coins from high-volume wallets which would kill any client. Coinb.in is in fact the ONLY WAY to do this, as even QT falls over around 600 UTXOs. You will see the total balance that was loaded in the Transaction Fee field. And also in the Inputs tab, where you can go to adjust which UTXOs to spend. Now you need to add the wallet(s) and amounts to send to them. Lets suppose the source contained a single UTXO for 1,000 Doge. You want to send 500 of them. So you would enter the #2 address in the Address field, and 500 in the Amount field. The Fee now changes to 500, which is not what you want. So you click the + button to bring up a new line, enter the change address and the other 500, making the fee zero. And you’re done. Check that the Fee is indeed zero. Check that the amounts shown in the Outputs and Inputs tabs match exactly.
THIS IS CRITICAL!
There is a bug which will send all the coins to the miners if the Outputs exceed the Inputs. I would have expected the Fee to show as negative in such a situation, but it doesn’t. BE WARNED! Once everything looks right, hit the Submit button. This will give you a block of hex code. Copy it. Sign Go to the Sign tab and paste it. Add your private key for the source wallet and click Submit. Note this can be done offline for safety. This will give you another block of hex, the SIGNED transaction. Broadcast Copy this and paste it in the Broadcast tab and click Submit. That’s it. Your coins are on their way. Make a cuppa and settle in while they arrive in a minute or three. Note: All fields retain their values unless you refresh the page! This can be a boon when doing multiple transactions, such as when emptying a huge wallet. But it can also be a trap for the unsuspecting. Refresh or close the window when you’re done.
Who?
Who should use this? Absolutely EVERYONE! Even if you’re wedded to your client in some satanic blood-contract, you should still know how this works, because sooner or later you’re going to have a problem you can’t fix without it. Definitely download the site and store it on every device you have. On every USB backup of your wallets. On your phone (well, except iOS which doesn’t do local HTML), etc, etc, etc. Oh, and if you’re a programmer SmartyShibe, do consider improving the code over on GitHub. EDIT:https://github.com/OutCast3k/coinbin added courtesy of AtomHearth
Why there isn't a zip file of the blockchain for the first 3 years for quick download?
So if the blockchain is a pain in the ass to download for the first time, why can not be in a zipfile for the first X years, and only the last few weeks or months need to be downloaded/upgraded? Is that really that hard to implement? If bitcoin will really take off, there will be more and more transactions, so the blockchain is getting bigger and longer faster, so it would make sense that past months would be in an easily handable zip file. Even if this zipfile updated just bimonthly, that means that new users need to download only the last 2 months transactions, the previous years should be a quick download....
Verify release signatures Download torrent Source code Show version history. Bitcoin Core Release Signing Keys v0.11.0+ 01EA5486DE18A882D4C2684590C8019E36C2E964 ... Bitcoin is a distributed, worldwide, decentralized digital money. Bitcoins are issued and managed without any central authority whatsoever: there is no government, company, or bank in charge of Bitcoin. You might be interested in Bitcoin if you like cryptography, distributed peer-to-peer systems, or economics. This is BTG Core Wallet / full node version v0.17.3. Thanks for running the Bitcoin Gold Core wallet! You are running a fully validating node that becomes part of the BTG network, improving security for everyone, even if you don’t use it for your personal transactions. Bitcoin Core is a community-driven free software project, released under the MIT license. Verify release signatures Download torrent Source code Show version history Bitcoin Core Release Signing Keys v0.8.6 - 0.9.2.1 v0.9.3 - 0.10.2 v0.11.0+ Coinbase is a secure platform that makes it easy to buy, sell, and store cryptocurrency like Bitcoin, Ethereum, and more. Based in the USA, Coinbase is available in over 30 countries worldwide.
How to sign and Verify messages with your Bitcoin Adress from your Softwarewallet
Basic explanation of how to sign and verify a Bitcoin Adress from your Softwarewallet, example client was Bitcoin-qt. Feel free to donate to keep more Tutorials coming: How to Download and Verify the Armory Bitcoin Wallet - Duration: 22:31. Rex Kneisley 5,163 views. ... How to verify software downloads with a cryptographic signature file Part 1 - Duration: ... 🍓 Best Bitcoin Mining Software That Work in 2020 ... How to Download & Verify the Bitcoin Core Wallet ... Rex Kneisley 18,412 views. 15:29. 6. bitcoin-qt - Duration: 6:50. 402 Payment ... Keep all your crypto safe & upgrade to a Ledger Nano X Hardware Wallet https://shop.ledger.com/pages/ledger-nano-x?r=5243ecbb8427 Alternatively, if you prefe... How to Download & Verify the Bitcoin Core Wallet - Duration: 15:29. Rex Kneisley 18,233 views. 15:29. Choose your Bitcoin Wallet - An in-depth review of BitcoinQT, ...
