Power of the Command Line (bitcoin-cli, hwi, electrum, trezorctl)
I think some of the console tools available with HW wallets today are greatly under utilized. Here's a quick write-up on how to create and sign a TXN very similar to 43d27...1fc06 found on the SLIP-14 wallet. I'll be using TrezorCTL, Electrum, and HWI for the signing. I won't go much into the setup or install, but feel free to ask if you have questions about it. Note, you don't have to use all three of these. Any one will produce a valid signed TXN for broadcast. I just showed how to do it three ways. Whats more some of the Electrum and HWI steps are interchangeable. ColdCard also has a utility called ckcc that will do the sign operation instead of HWI, but in many ways they are interchangeable. KeepKey and Ledger both have libraries for scripted signing but no one-shot, one-line console apps that I know of. But HWI and Electrum of course work on all four.
TrezorCTL
This is the what most would think of to use to craft and sign TXNs, and is definitely very simple. The signing uses a script called build_tx.py to create a JSON file that is then used by the btc sign-tx command. The whole process is basically:
tools/build_tx.py | trezorctl btc sign-tx -
This just means, take the output of build_tx and sign it. To copy 43d27...1fc06, I wrote a small script to feed build_tx, so my process looks like:
secho() { sleep 1; echo $*} secho "Testnet" # coin name secho "tbtc1.trezor.io" # blockbook server and outpoint (below) secho "e294c4c172c3d87991b0369e45d6af8584be92914d01e3060fad1ed31d12ff00:0" secho "m/84'/1'/0'/0/0" # prev_out derivation to signing key secho "4294967293" # Sequence for RBF; hex(-3) secho "segwit" # Signature type on prev_out to use secho "" # NACK to progress to outs secho "2MsiAgG5LVDmnmJUPnYaCeQnARWGbGSVnr3" # out[0].addr secho "10000000" # out[1].amt secho "tb1q9l0rk0gkgn73d0gc57qn3t3cwvucaj3h8wtrlu" # out[1].addr secho "20000000" # out[1].amt secho "tb1qejqxwzfld7zr6mf7ygqy5s5se5xq7vmt96jk9x" # out[2].addr secho "99999694" # out[2].amt secho "" # NACK to progress to change secho "" # NACK to skip change secho "2" # txn.version secho "0" # txn.locktime ```
Electrum
Electrum is one of the better GUI wallets available, but it also has a pretty good console interface. Like before you need your Trezor with the SLIP-14 wallet loaded and paired to Electrum. I'll assume Electrum is up and running with the Trezor wallet loaded to make things simple. Like with TrezorCTL, Electrum feeds on a JSON file, but unlike TrezorCTL it needs that JSON squished into the command line. This is a simple sed command, but I won't bore you with the details, but just assume that's done. So the process in Electrum (v4.0.3) looks like:
electrum serialize (create psbt to sign)
electrum --wallet signtransaction (sign said psbt)
Still pretty simple right! Below is the JSON I smushed for #1
HWI is an unsung hero in my book. It's a very small clean and simple interface between HW wallets and Bitcoin Core. It currently supports a good range of HW wallets. It keeps itself narrowly focused on TXN signing and offloads most everything else to Bitcoin Core. Again, I'll assume you've imported your Trezor keypool into Core and done the requisite IBD and rescan. And if you don't have the RPC enabled, you can always clone these commands into the QT-console. To sign our TXN in HWI (v1.1.2), we will first need to craft (and finalize) it in Bitcoin Core (0.21.1). Like in Electrum, we will have to use simple sed to smush some JSON into command arguments, but I'll assume you have that covered. It will take an inputs.json and an outputs.json named separately.
This may all seem like very low level coding, but is surprisingly simple once you get a knack for it. Whats more, all these platforms support testnet which allows you to practice with valueless coins until you get the hang of it. And, like many things in bitcoin, this is all (mostly) python, which is one of the easier languages to learn. Enjoy Footnotes 1 - https://github.com/trezotrezor-firmware/issues/1296
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)
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
Power of the Command Line (bitcoin-cli, hwi, electrum, trezorctl)
I think some of the console tools available with HW wallets today are greatly under utilized. Here's a quick write-up on how to create and sign a TXN very similar to 43d27...1fc06 found on the SLIP-14 wallet. I'll be using TrezorCTL, Electrum, and HWI for the signing. I won't go much into the setup or install, but feel free to ask if you have questions about it. Note, you don't have to use all three of these. Any one will produce a valid signed TXN for broadcast. I just showed how to do it three ways. Whats more some of the Electrum and HWI steps are interchangeable.
TrezorCTL
This is the what most would think of to use to craft and sign TXNs, and is definitely very simple. The signing uses a script called build_tx.py to create a JSON file that is then used by the btc sign-tx command. The whole process is basically:
tools/build_tx.py | trezorctl btc sign-tx -
This just means, take the output of build_tx and sign it. To copy 43d27...1fc06, I wrote a small script to feed build_tx, so my process looks like:
secho() { sleep 1; echo $*} secho "Testnet" # coin name secho "tbtc1.trezor.io" # blockbook server and outpoint (below) secho "e294c4c172c3d87991b0369e45d6af8584be92914d01e3060fad1ed31d12ff00:0" secho "m/84'/1'/0'/0/0" # prev_out derivation to signing key secho "4294967293" # Sequence for RBF; hex(-3) secho "segwit" # Signature type on prev_out to use secho "" # NACK to progress to outs secho "2MsiAgG5LVDmnmJUPnYaCeQnARWGbGSVnr3" # out[0].addr secho "10000000" # out[1].amt secho "tb1q9l0rk0gkgn73d0gc57qn3t3cwvucaj3h8wtrlu" # out[1].addr secho "20000000" # out[1].amt secho "tb1qejqxwzfld7zr6mf7ygqy5s5se5xq7vmt96jk9x" # out[2].addr secho "99999694" # out[2].amt secho "" # NACK to progress to change secho "" # NACK to skip change secho "2" # txn.version secho "0" # txn.locktime ```
Electrum
Electrum is one of the better GUI wallets available, but it also has a pretty good console interface. Like before you need your Trezor with the SLIP-14 wallet loaded and paired to Electrum. I'll assume Electrum is up and running with the Trezor wallet loaded to make things simple. Like with TrezorCTL, Electrum feeds on a JSON file, but unlike TrezorCTL it needs that JSON squished into the command line. This is a simple sed command, but I won't bore you with the details, but just assume that's done. So the process in Electrum (v4.0.3) looks like:
electrum serialize (create psbt to sign)
electrum --wallet signtransaction (sign said psbt)
Still pretty simple right! Below is the JSON I smushed for #1
HWI is an unsung hero in my book. It's a very small clean and simple interface between HW wallets and Bitcoin Core. It currently supports a good range of HW wallets. It keeps itself narrowly focused on TXN signing and offloads most everything else to Bitcoin Core. Again, I'll assume you've imported your Trezor keypool into Core and done the requisite IBD and rescan. And if you don't have the RPC enabled, you can always clone these commands into the QT-console. To sign our TXN in HWI (v1.1.2), we will first need to craft (and finalize) it in Bitcoin Core (0.21.1). Like in Electrum, we will have to use simple sed to smush some JSON into command arguments, but I'll assume you have that covered. It will take an inputs.json and an outputs.json named separately.
This may all seem like very low level coding, but is surprisingly simple once you get a knack for it. Whats more, all these platforms support testnet which allows you to practice with valueless coins until you get the hang of it. And, like many things in bitcoin, this is all (mostly) python, which is one of the easier languages to learn. Enjoy Footnotes 1 - https://github.com/trezotrezor-firmware/issues/1296
Syscoin Platform’s Great Reddit Scaling Bake-off Proposal
https://preview.redd.it/rqt2dldyg8e51.jpg?width=1044&format=pjpg&auto=webp&s=777ae9d4fbbb54c3540682b72700fc4ba3de0a44 We are excited to participate and present Syscoin Platform's ideal characteristics and capabilities towards a well-rounded Reddit Community Points solution! Our scaling solution for Reddit Community Points involves 2-way peg interoperability with Ethereum. This will provide a scalable token layer built specifically for speed and high volumes of simple value transfers at a very low cost, while providing sovereign ownership and onchain finality. Token transfers scale by taking advantage of a globally sorting mempool that provides for probabilistically secure assumptions of “as good as settled”. The opportunity here for token receivers is to have an app-layer interactivity on the speed/security tradeoff (99.9999% assurance within 10 seconds). We call this Z-DAG, and it achieves high-throughput across a mesh network topology presently composed of about 2,000 geographically dispersed full-nodes. Similar to Bitcoin, however, these nodes are incentivized to run full-nodes for the benefit of network security, through a bonded validator scheme. These nodes do not participate in the consensus of transactions or block validation any differently than other nodes and therefore do not degrade the security model of Bitcoin’s validate first then trust, across every node. Each token transfer settles on-chain. The protocol follows Bitcoin core policies so it has adequate code coverage and protocol hardening to be qualified as production quality software. It shares a significant portion of Bitcoin’s own hashpower through merged-mining. This platform as a whole can serve token microtransactions, larger settlements, and store-of-value in an ideal fashion, providing probabilistic scalability whilst remaining decentralized according to Bitcoin design. It is accessible to ERC-20 via a permissionless and trust-minimized bridge that works in both directions. The bridge and token platform are currently available on the Syscoin mainnet. This has been gaining recent attention for use by loyalty point programs and stablecoins such as Binance USD.
Solutions
Syscoin Foundation identified a few paths for Reddit to leverage this infrastructure, each with trade-offs. The first provides the most cost-savings and scaling benefits at some sacrifice of token autonomy. The second offers more preservation of autonomy with a more narrow scope of cost savings than the first option, but savings even so. The third introduces more complexity than the previous two yet provides the most overall benefits. We consider the third as most viable as it enables Reddit to benefit even while retaining existing smart contract functionality. We will focus on the third option, and include the first two for good measure.
Distribution, burns and user-to-user transfers of Reddit Points are entirely carried out on the Syscoin network. This full-on approach to utilizing the Syscoin network provides the most scalability and transaction cost benefits of these scenarios. The tradeoff here is distribution and subscription handling likely migrating away from smart contracts into the application layer.
The Reddit Community Points ecosystem can continue to use existing smart contracts as they are used today on the Ethereum mainchain. Users migrate a portion of their tokens to Syscoin, the scaling network, to gain much lower fees, scalability, and a proven base layer, without sacrificing sovereign ownership. They would use Syscoin for user-to-user transfers. Tips redeemable in ten seconds or less, a high-throughput relay network, and onchain settlement at a block target of 60 seconds.
Integration between Matic Network and Syscoin Platform - similar to Syscoin’s current integration with Ethereum - will provide Reddit Community Points with EVM scalability (including the Memberships ERC777 operator) on the Matic side, and performant simple value transfers, robust decentralized security, and sovereign store-of-value on the Syscoin side. It’s “the best of both worlds”. The trade-off is more complex interoperability.
Syscoin + Matic Integration
Matic and Blockchain Foundry Inc, the public company formed by the founders of Syscoin, recently entered a partnership for joint research and business development initiatives. This is ideal for all parties as Matic Network and Syscoin Platform provide complementary utility. Syscoin offers characteristics for sovereign ownership and security based on Bitcoin’s time-tested model, and shares a significant portion of Bitcoin’s own hashpower. Syscoin’s focus is on secure and scalable simple value transfers, trust-minimized interoperability, and opt-in regulatory compliance for tokenized assets rather than scalability for smart contract execution. On the other hand, Matic Network can provide scalable EVM for smart contract execution. Reddit Community Points can benefit from both. Syscoin + Matic integration is actively being explored by both teams, as it is helpful to Reddit, Ethereum, and the industry as a whole.
Total cost for these 100k transactions: $0.63 USD See the live fee comparison for savings estimation between transactions on Ethereum and Syscoin. Below is a snapshot at time of writing: ETH price: $318.55 ETH gas price: 55.00 Gwei ($0.37) Syscoin price: $0.11 Snapshot of live fee comparison chart Z-DAG provides a more efficient fee-market. A typical Z-DAG transaction costs 0.0000582 SYS. Tokens can be safely redeemed/re-spent within seconds or allowed to settle on-chain beforehand. The costs should remain about this low for microtransactions. Syscoin will achieve further reduction of fees and even greater scalability with offchain payment channels for assets, with Z-DAG as a resilience fallback. New payment channel technology is one of the topics under research by the Syscoin development team with our academic partners at TU Delft. In line with the calculation in the Lightning Networks white paper, payment channels using assets with Syscoin Core will bring theoretical capacity for each person on Earth (7.8 billion) to have five on-chain transactions per year, per person, without requiring anyone to enter a fee market (aka “wait for a block”). This exceeds the minimum LN expectation of two transactions per person, per year; one to exist on-chain and one to settle aggregated value.
Sysethereum Dapp: UI Dapp for reference implementation. The Sysethereum-Dapp automates the process flows depicted in “Syscoin Bridge & How it Works” within a native ReactJS application for convenience. An active implementation using the Syscoin Platform Mainnet can be used atbridge.syscoin.org.
API
Tools to simplify using Syscoin Bridge as a service with dapps and wallets will be released some time after implementation of Syscoin Core 4.2. These will be based upon the same processes which are automated in the current live Sysethereum Dapp that is functioning with the Syscoin mainnet.
The Syscoin Ethereum Bridge is secured by Agent nodes participating in a decentralized and incentivized model that involves roles of Superblock challengers and submitters. This model is open to participation. The benefits here are trust-minimization, permissionless-ness, and potentially less legal/regulatory red-tape than interop mechanisms that involve liquidity providers and/or trading mechanisms. The trade-off is that due to the decentralized nature there are cross-chain settlement times of one hour to cross from Ethereum to Syscoin, and three hours to cross from Syscoin to Ethereum. We are exploring ways to reduce this time while maintaining decentralization via zkp. Even so, an “instant bridge” experience could be provided by means of a third-party liquidity mechanism. That option exists but is not required for bridge functionality today. Typically bridges are used with batch value, not with high frequencies of smaller values, and generally it is advantageous to keep some value on both chains for maximum availability of utility. Even so, the cross-chain settlement time is good to mention here.
Cost
Ethereum -> Syscoin: Matic or Ethereum transaction fee for bridge contract interaction, negligible Syscoin transaction fee for minting tokens Syscoin -> Ethereum: Negligible Syscoin transaction fee for burning tokens, 0.01% transaction fee paid to Bridge Agent in the form of the ERC-20, Matic or Ethereum transaction fee for contract interaction.
Z-DAG
Zero-Confirmation Directed Acyclic Graph is an instant settlement protocol that is used as a complementary system to proof-of-work (PoW) in the confirmation of Syscoin service transactions. In essence, a Z-DAG is simply a directed acyclic graph (DAG) where validating nodes verify the sequential ordering of transactions that are received in their memory pools. Z-DAG is used by the validating nodes across the network to ensure that there is absolute consensus on the ordering of transactions and no balances are overflowed (no double-spends).
Benefits
Unique fee-market that is more efficient for microtransaction redemption and settlement
Uses decentralized means to enable tokens with value transfer scalability that is comparable or exceeds that of credit card networks
Provides high throughput and secure fulfillment even if blocks are full
Probabilistic and interactive
99.9999% security assurance within 10 seconds
Can serve payment channels as a resilience fallback that is faster and lower-cost than falling-back directly to a blockchain
Each Z-DAG transaction also settles onchain through Syscoin Core at 60-second block target using SHA-256 Proof of Work consensus
Z-DAG enables the ideal speed/security tradeoff to be determined per use-case in the application layer. It minimizes the sacrifice required to accept and redeem fast transfers/payments while providing more-than-ample security for microtransactions. This is supported on the premise that a Reddit user receiving points does need security yet generally doesn’t want nor need to wait for the same level of security as a nation-state settling an international trade debt. In any case, each Z-DAG transaction settles onchain at a block target of 60 seconds.
Syscoin Specs
Syscoin 3.0 White Paper (4.0 white paper is pending. For improved scalability and less blockchain bloat, some features of v3 no longer exist in current v4: Specifically Marketplace Offers, Aliases, Escrow, Certificates, Pruning, Encrypted Messaging)
16MB block bandwidth per minute assuming segwit witness carrying transactions, and transactions ~200 bytes on average
SHA256 merge mined with Bitcoin
UTXO asset layer, with base Syscoin layer sharing identical security policies as Bitcoin Core
Z-DAG on asset layer, bridge to Ethereum on asset layer
On-chain scaling with prospect of enabling enterprise grade reliable trustless payment processing with on/offchain hybrid solution
Focus only on Simple Value Transfers. MVP of blockchain consensus footprint is balances and ownership of them. Everything else can reduce data availability in exchange for scale (Ethereum 2.0 model). We leave that to other designs, we focus on transfers.
Future integrations of MAST/Taproot to get more complex value transfers without trading off trustlessness or decentralization.
Zero-knowledge Proofs are a cryptographic new frontier. We are dabbling here to generalize the concept of bridging and also verify the state of a chain efficiently. We also apply it in our Digital Identity projects at Blockchain Foundry (a publicly traded company which develops Syscoin softwares for clients). We are also looking to integrate privacy preserving payment channels for off-chain payments through zkSNARK hub & spoke design which does not suffer from the HTLC attack vectors evident on LN. Much of the issues plaguing Lightning Network can be resolved using a zkSNARK design whilst also providing the ability to do a multi-asset payment channel system. Currently we found a showstopper attack (American Call Option) on LN if we were to use multiple-assets. This would not exist in a system such as this.
Wallets
Web3 and mobile wallets are under active development by Blockchain Foundry Inc as WebAssembly applications and expected for release not long after mainnet deployment of Syscoin Core 4.2. Both of these will be multi-coin wallets that support Syscoin, SPTs, Ethereum, and ERC-20 tokens. The Web3 wallet will provide functionality similar to Metamask. Syscoin Platform and tokens are already integrated with Blockbook. Custom hardware wallet support currently exists via ElectrumSys. First-class HW wallet integration through apps such as Ledger Live will exist after 4.2. Current supported wallets Syscoin Spark Desktop Syscoin-Qt
Thank you for close consideration of our proposal. We look forward to feedback, and to working with the Reddit community to implement an ideal solution using Syscoin Platform!
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
People had been speculating since the dawn of crypto when the world’s largest online marketplaces, the ones of the Amazon caliber like eBay, Etsy or AliExpress, and, well, Amazon itself, would start to accept cryptocurrencies. There were a slew of rumors, opinions, and theories thickly interspersed with false reports popping up here and there of Amazon and its little cousins being on the verge of embracing cryptocurrencies. On top of that, someone has actually posted a petition on change.org to add Ether to Amazon as a payment method. by StealthEX Long story short, that was a waste of time. High hopes fell flat, and people lost religion. But not all. As the common wisdom goes, when hope dies, action begins. This exposition describes one such effort which tries to bring to fruition the idea of a decentralized marketplace for trading goods and services. And as you might have already figured it out, with a cryptocurrency as a means of payment. So let’s welcome Particl Marketplace and see what it has to offer – and what Amazon has missed.
What is it, in simple words?
Particl Marketplace is an online marketplace where you can trade goods and services. Not a big deal, you may think. However, what distinguishes it from places like Amazon as well as cryptocurrency-enabled marketplaces is the decentralized nature of purchases on Particl. You can think of it as a variety of a decentralized cryptocurrency exchange (aka DEX) where trades are being conducted on-chain. But in case of Particl, it is goods and services that are being traded, not fiat or crypto, with deals on-chain as well, fully encrypted and decentralized. Particl is a global peer-to-peer privacy-centered marketplace that uses an automated two-party escrow system. It is crypto-agnostic and designed to work with any cryptocurrency, creating a secure, highly-scalable environment supported by a privacy-focused blockchain-based platform. The team behind the project sees its mission in developing “a new decentralized, private and democratic economy” that is governed by the network of its users, with no central authority or middleman getting in the way. In the project developers’ own words, Particl enables everyone to participate in a free, anonymous exchange of all kinds of goods, without paying any fee and regardless of geographical location. To be sure, you are already thinking about Silk Road and its dark fate, and that the government is going to crack down monumentally on Particl one day. Well, the outcome may vary as the payments on the platform are made using its own cryptocurrency PART, with its laser focus on privacy and anonymity. But more on this later.
How did it grow up?
The development of the Particl project started in early 2017 with the release of the white paper describing the team’s vision for the marketplace, which was shortly followed by a successful seed funding that brought in enough funds ($750,000) to support the development of the project for a year (it turned out sufficient to last for over two years). These donations helped to establish the Particl Foundation, a non-profit Swiss organization with the goal of providing legal protection for the project to ensure its sustained development and compliance with government regulations. It receives 10% of all the staking rewards generated on the Particl network, making the project self-sustainable and free for most uses. Unlike other such projects in the crypto arena, Particl has been using its own blockchain from day one, which happened to be July 17, 2017. It was specifically designed to be crypto agnostic by supporting and working with any cryptocurrency. Additionally, it supported the smart contract tech out of the box, giving users an ability to build all kinds of decentralized applications (dApps) that can be directly integrated into the Particl marketplace. On May 31, 2018, the Particl Marketplace, the Holy Grail of the entire endeavor, was made available for alpha testing on the testnet of the project, which later split into development and stable branches. It went live with the mainnet release of the Particl Open Marketplace on August 12, 2019, which featured Particl Desktop 2.0.0, a client-side application providing user interface and built-in wallet functions. On November 25, 2019, the Particl Desktop 2.3.0 client was released that enabled Bitcoin payments and marked the introduction of untraceable transactions. With the help of the new in-wallet exchange module, everyone can easily swap their bitcoins for the native PART coin. Moreover, the module allows seamless integration of third-party accountless exchange services right into the marketplace, with StealthEX being one of them.
How is it different from other marketplaces?
The common solution many P2P marketplaces implement to protect buyers and sellers from the other party failing to honor their end of the bargain is through third-party escrow, where the “third-party” in the majority of places and cases is the platform itself that the market participants must mutually trust. In short, it is a single point of failure. And the selling (pardon the pun) point of the entire Particl’s marketplace is its decentralized escrow, which is a thing entirely between the two parties engaged. No middlemen allowed here! And these are not empty words. Particl implements the concept best known as Mutually Assured Destruction (aptly shortened as MAD), a military doctrine you are certainly familiar with, and probably even afraid of, that consists in a mutual destruction of two belligerent parties in an all-out nuclear holocaust. If you are curious, the idea stems from the game theory and has a lot to do with the Nash Equilibrium, of John Nash’s fame. In a nutshell, Particl removes the need for a trusted escrow agent by introducing MAD escrow smart contracts. A MAD escrow contract allows to lock funds in a multi-signature address that can be released only if all the parties sign off on the transaction. So both the seller and the buyer lock in the contract an agreed amount for a specified period of time, with the buyer also depositing the payment for the items purchased. The escrowed funds are released when both parties confirm the fulfillment of the agreement. Should one party break the terms, the funds remain locked for good causing a mutual financial loss until both parties agree to sign off. Another crucial aspect of Particl Marketplace is its end-to-end privacy. The problem with conventional marketplaces acting as an escrow agent is that the communication between the parties should be open to the agent for it to serve as an arbitrator. With Particl, it is no longer required, and all messages between the buyer and the seller are encrypted. Despite being public, only their recipient can decrypt them, which effectively makes messages untraceable. This is also where the PART coin turns up quite handy. It enables three different privacy modes, and with the most secure mode, the Anon mode, PART transactions utilize the RingCT privacy protocol, which hides both the amount transferred and the identity of the parties transacting. Accordingly, every part of the entire Particl trading environment is thoroughly decentralized, and the full anonymity of market participants is maintained at all times, making the platform a completely trustless marketplace. Big Brother is no longer watching you. Aside from that, you can stake PART and generate a source of passive income for yourself. Particl uses a custom Proof-of-Stake consensus protocol, allowing you to get a piece of the pie in the form of new coins created at each block according to the scheduled inflation process. The annual inflation rate is initially set to 5% and goes down 1 percentage point every year until it finally floors at 2% indefinitely. Moreover, these rates are a bare minimum as they assume that all PART coins have been staked. Otherwise, the income will be bigger and better as the same rewards are paid to fewer coins. Additionally, your passive income through staking PART will be augmented by the fees generated through the everyday marketplace operations. Whether it is network fees collected via PART transactions or marketplace listing fees paid by the sellers, all of them contribute to the stakers’ rewards. At the end of the day, staking PART can turn into a profitable business once the Particl platform starts to attract more traffic. In simple words, the more popular the market gets, the more fees it generates, the more coins the stakers earn. As PART is a standalone cryptocurrency, it can be used outside Particl Marketplace as well. So if you plan on using it for purposes other than eCommerce, it is traded on several exchanges, for example, HitBTC and Bittrex, with more exchanges to list PART in the future. There are native Particl wallets available for storing PART such as Particl Qt with Ledger support, Particl-cli, and Particl Copay Wallet, with the latter available for both the desktop and the mobile. There is also a third-party multicurrency Flare Wallet, enabling cold staking for Particl. Running Particl is a collective effort, which means no operational costs and no company bagging profits from it. The marketplace buyers don’t pay any commissions other than tiny network confirmation fees, while the sellers are only charged a small listing fee to keep spam listings to a minimum. This creates a highly competitive environment, with the sellers making more profits and the buyers having access to cheaper goods and services as a result.
What’s in the pipeline?
The next major release of the Particl Marketplace should have been Particl Desktop 2.4.0, but it was later rebranded as Particl Desktop 3.0 to reflect its breakthrough nature. It is set for release in the second half of 2020 and will enable the addition of user-created markets and storefronts, effectively turning the Particl marketplace into a network of specialized markets. And if you think about it, that makes perfect sense. Say, you have a social network account highly merited and full of karma that you want to sell, whatever your reasons might be. Then creating a dedicated market for trading such accounts privately and securely may look extremely appealing to you. Whether it is the right thing to do is another matter, of course. Kidding aside, it is obviously not about selling or offering something that the society on the whole doesn’t approve of or frowns upon. If you are a freelancer, for example, a graphics designer or a translator, you would be certainly interested in the future freelancer markets – along with your potential employers. Put simply, birds of a feather should flock together. To keep things in perspective, popular freelancer markets that exist today charge up to 10-20% of what you would get from your client if you negotiated directly. All in all, establishing communities across the marketplace seems to be the next logical step in the natural evolution and growth of the platform. In fact, it is a little surprising that the Particl team didn’t come up with this idea earlier. Meanwhile, we wish Particl success and good luck in achieving their goals and aspirations. And remember if you need to exchange your coins StealthEX is here for you. We provide a selection of more than 250 coins and constantly updating the list so that our customers will find a suitable option. Our service does not require registration and allows you to remain anonymous. Why don’t you check it out? Just go to StealthEX and follow these easy steps: ✔ Choose the pair and the amount for your exchange. For example ETH to PART. ✔ Press the “Start exchange” button. ✔ Provide the recipient address to which the coins will be transferred. ✔ Move your cryptocurrency for the exchange. ✔ Receive your PART coins! Follow us on Medium, Twitter, Facebook, and Reddit to get StealthEX.io updates and the latest news about the crypto world. For all requests message us via [email protected]. The views and opinions expressed here are solely those of the author. Every investment and trading move involves risk. You should conduct your own research when making a decision. Original article was posted onhttps://stealthex.io/blog/2020/08/26/particl-marketplace-where-sellers-meet-buyers/
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.
I’m a longtime blockchain enthusiast and developer and one of my biggest gripes about this space is how quickly every new project is widely dismissed as a “scam” or “shitcoin” by so many people before it even gets off the ground. Sure, there is a lot of uncharted territory with pirates lurking to steal your bags left and right but with asmall amount of personal educationyou can exist safely in the world of crypto I promise! With this article I aim to help lift your knowledge a little higher while helping keep your funds a little safer!
So What Is Happening?
On Tuesday February 18, 2020 a new coin named Ring (RNG) will be minted. This coin aims to bring two unique and fresh methods of proofing to the crypto game, quite literally: Agent-Based Hive Mining (borrowed from LCC) and Proof-of-Play Mining, where literal gameplay is used to hash and reward miners! To celebrate and help spread the word, the team is giving away claims of free RNG to all holders of the following coins:
Litecoin Cash (LCC)
Bitcoin (BTC)
Dash (DASH)
Dogecoin (DOGE)
It's being touted as the world's first crypto "4-way fork" but I'd really call it more of a "4-way claim" since its a brand new chain and not based on the code of any of the rewarded coins. It's simply a clever method of allowing a wider range of coin holders a chance to participate in the launch of these exciting new features!
How Will This Process Work?
On the 18th of February, a balance snapshot will be taken of the four chains listed above. Anyone holding a balance with any of these coins at the time of the snapshot will be forever eligible to claim their RNG at any time. Because the only way to prove ownership of a crypto address is to supply the private keys, and pretty much EVERYONE will tell you to guard those things with your life, below I will outline exactly what to do so there is absolutely 0% risk of losing a single satoshi! This method will apply to ANY claim rewards of any coin in the future as well. Always practice #SafeForking!
How Do I Safely Claim My RNG?
STEP 1 -- BEFORE THE SNAPSHOT -- VERIFY ACCESS TO YOUR PRIVATE KEYS All core wallets will allow you to export a private key of any address in your wallet but many third party services like exchanges and hot wallets do not allow access to them. In these cases you will need to send your funds out of the third party service and into some kind of personal wallet where you can reach the private keys yourself. Then just wait for the snapshot to happen…
To make thingseasieron yourself, you canoptionallycollect your original coins into as few addresses as possibleBEFOREthe snapshot. Doing so reduces the number of keys you will need to empty and import later. It’s justless work!
\** SNAPSHOT HAPPENS HERE... **** STEP 2 -- ATER THE SNAPSHOT -- EMPTY ALL ADDRESSES YOU WISH TO CLAIM After the snapshot is confirmed, withdraw all coins OUT of each of your origin coin addresses into brand new addresses leaving the original ones quite empty. This way when you import later there is NO risk of losing anything! Also know that after you import these private keys you should never use them again for safety’s sake! It’s kind of the whole reason you’re even reading this article in the first place. STEP 3 -- EXPORT PRIVATE KEYS FOR ALL ADDRESS YOU WISH TO CLAIM This is the most difficult part, are you ready? Once each claim address is confirmed to be EMPTY, you must obtain each one’s private keys. This will entirely depend on the wallet you use (QT example below) but for all core wallets there is generally an option for exporting private keys somewhere in there. Collect them all!
How to Export QT Wallet Private Keys:⛔️— DISABLE INTERNET FOR SAFETY —⛔️- Open theQT wallet client-Click onHELPin the menu bar- Click onDEBUG WINDOW-Click on theCONSOLEtab- Click inside theinput boxat the bottom(if your wallet is locked…)- Type:walletpassphrase [Password] 600(this unlocks your wallet for 10 minutes)- Type:dumpprivkey [Address]-Copythe output hash,pasteit into a list somewhere.(repeat as needed, clear your clipboard history after)-Type:walletlock(if applicable)⚡— RE-ENABLE YOUR INTERNET —⚡
STEP 4 -- IMPORT ALL PRIVATE KEYS INTO RNG CORE WALLET \** PLEASE VERIFY THAT EVERY CLAIM ADDRESS IS EMPTY BEFORE CONTINUING... **** The final step is to simply import each of these private keys into the new Ring Core Wallet to claim your free RNG rewards. The wallet handles this part automatically and you will see your new RNG balance right away. You can find this option under the File > Import Private Keys menu.
Importing a private key is theonly wayto prove ownership of a crypto address so this is unavoidable if you want to claim new coins from it. The steps above will allow you toprove ownershipof your snapshotted address balance plususe its empty keyto thenclaim your new coinsthus keeping your original coinscompletely protectedin the brand new address with anew private key(which you should now also keepVERY private!) By emptying the addressbeforeyou import it’s private key youeliminatethe risk of theft entirely. One cannot take from analready emptyjar. It should also be noted toNEVERuse the imported address again as an addedsafety precaution*!*
👏👏👏 DONE! ENJOY YOUR FREE MONEY! 👏👏👏
How Much RNG Will I Receive?
Litecoin Cash holders will receive the highest claim ratio (5000 LCC = 1 RNG) as the LCC team are the ones responsible for creating Ring and wanted to extend a heart-felt thank you to the LCC community for their years of support. All other coins will be based on a 1:1 ratio with the value of Bitcoin at the time of the fork. This of course means 1 BTC = 1 RNG. For DASH and DOGE, however, their BTC market prices will determine their reward ratios. (For example ifDASHis trading at0.015 BTCeach, then eachDASHcoin will net you a reward of0.015 RNGto match.) Of course you don't need whole coins to claim, partial decimals work just fine!
What Value Will RNG Have?
That, my friends, is entirely up to the markets. No one in the history of crypto has had a perfect track record of price predictions so I'm not even going to try here. I will say, though, having gotten to play with their Testnet a bit so far that I am very impressed with the new Proof-of-Play method and how they have initially implemented it. It bodes very good things for the future of their project and this coin so I personally would expect its value to hold and most likely rise steadily as more people become aware of this groundbreaking new tech and it's potential to expand outward!
Is Litecoin Cash Still Going To Exist?
Absolutely! At least, from what I can gather. LCC has it's own purposes and will continue to be developed on. Ring is not meant to be a replacement or upgrade of any kind to Litecoin Cash. It is an entirely different proofing algorithm and a different mission statement altogether. It's more so meant to help expose the amazing new technologies developed on the LCC blockchain to a wider audience beyond simply its own fan base. If anything it'll act a sister chain that can help expose more folks to LCC in the future!
Disclaimer
While I am a moderator for the Litecoin Cash Discord server, I am writing this from an independent point of view as an educated crypto enthusiast with a passion for helping others navigate these waters. Having been an initial forker and third party developer on top of LCC myself, I feel I have some valuable insight into the direction the team is taking and I wanted to offer some sound advice for the upcomingRing forkbefore the FUD gets caked on too thick. I know a lot of people get scared easily in crypto because of the rampant scamming that goes on but I've watched this team work their asses off for two years to get out from under the stain of Charlie Lee's very biased, uneducated "its a scam" tweet which was endlessly parroted throughout the Litecoin community with nothing but blind party loyalty and no due diligence. The LCC folks arekind, wonderful hard-working peoplewith big hearts and ambition and they have actually developed aunique proofing methodologythat is likely going to impress a lot of people! So before you go jumping on the "it's just another shitcoin" bandwagon please stop and take a real hard look at bothLitecoin Cash (LCC)andRing (RNG):two viable projects with something to bring to the table! If nothing else, hey, just claim your new coins and dump them off for some free money. You literally cannot lose if youPRACTICE SAFE FORKING!!! Good luck, cryptonauts! =A=
I’m a longtime blockchain enthusiast and developer and one of my biggest gripes about this space is how quickly every new project is widely dismissed as a “scam” or “shitcoin” by so many people before it even gets off the ground. Sure, there is a lot of uncharted territory with pirates lurking to steal your bags left and right but with asmall amount of personal educationyou can exist safely in the world of crypto I promise! With this article I aim to help lift your knowledge a little higher while helping keep your funds a little safer!
So What Is Happening?
On Tuesday February 18, 2020 a new coin named Ring (RNG) will be minted. This coin aims to bring two unique and fresh methods of proofing to the crypto game, quite literally: Agent-Based Hive Mining (borrowed from LCC) and Proof-of-Play Mining, where literal gameplay is used to hash and reward miners! To celebrate and help spread the word, the team is giving away claims of free RNG to all holders of the following coins:
Litecoin Cash (LCC)
Bitcoin (BTC)
Dash (DASH)
Dogecoin (DOGE)
It's being touted as the world's first crypto "4-way fork" but I'd really call it more of a "4-way claim" since its a brand new chain and not based on the code of any of the rewarded coins. It's simply a clever method of allowing a wider range of coin holders a chance to participate in the launch of these exciting new features!
How Will This Process Work?
On the 18th of February, a balance snapshot will be taken of the four chains listed above. Anyone holding a balance with any of these coins at the time of the snapshot will be forever eligible to claim their RNG at any time. Because the only way to prove ownership of a crypto address is to supply the private keys, and pretty much EVERYONE will tell you to guard those things with your life, below I will outline exactly what to do so there is absolutely 0% risk of losing a single satoshi! This method will apply to ANY claim rewards of any coin in the future as well. Always practice #SafeForking!
How Do I Safely Claim My RNG?
STEP 1 -- BEFORE THE SNAPSHOT -- VERIFY ACCESS TO YOUR PRIVATE KEYS All core wallets will allow you to export a private key of any address in your wallet but many third party services like exchanges and hot wallets do not allow access to them. In these cases you will need to send your funds out of the third party service and into some kind of personal wallet where you can reach the private keys yourself. Then just wait for the snapshot to happen…
To make thingseasieron yourself, you canoptionallycollect your original coins into as few addresses as possibleBEFOREthe snapshot. Doing so reduces the number of keys you will need to empty and import later. It’s justless work!
\** SNAPSHOT HAPPENS HERE... **** STEP 2 -- ATER THE SNAPSHOT -- EMPTY ALL ADDRESSES YOU WISH TO CLAIM After the snapshot is confirmed, withdraw all coins OUT of each of your origin coin addresses into brand new addresses leaving the original ones quite empty. This way when you import later there is NO risk of losing anything! Also know that after you import these private keys you should never use them again for safety’s sake! It’s kind of the whole reason you’re even reading this article in the first place. STEP 3 -- EXPORT PRIVATE KEYS FOR ALL ADDRESS YOU WISH TO CLAIM This is the most difficult part, are you ready? Once each claim address is confirmed to be EMPTY, you must obtain each one’s private keys. This will entirely depend on the wallet you use (QT example below) but for all core wallets there is generally an option for exporting private keys somewhere in there. Collect them all!
How to Export QT Wallet Private Keys: ⛔️ — DISABLE INTERNET FOR SAFETY — ⛔️ - Open the QT wallet client - Click on HELP in the menu bar - Click on DEBUG WINDOW - Click on the CONSOLE tab - Click inside the input box at the bottom (if your wallet is locked…) Type: walletpassphrase [Password] 600 (this unlocks your wallet for 10 minutes) - Type: dumpprivkey [Address] - Copy the output hash, paste it into a list somewhere. (repeat as needed, clear your clipboard history after) - Type: walletlock (if applicable) ⚡ — RE-ENABLE YOUR INTERNET — ⚡ DONE!
STEP 4 -- IMPORT ALL PRIVATE KEYS INTO RNG CORE WALLET \** PLEASE VERIFY THAT EVERY CLAIM ADDRESS IS EMPTY BEFORE CONTINUING... **** The final step is to simply import each of these private keys into the new Ring Core Wallet to claim your free RNG rewards. The wallet handles this part automatically and you will see your new RNG balance right away. You can find this option under the File > Import Private Keys menu.
Importing a private key is theonly wayto prove ownership of a crypto address so this is unavoidable if you want to claim new coins from it. The steps above will allow you toprove ownershipof your snapshotted address balance plususe its empty keyto thenclaim your new coinsthus keeping your original coinscompletely protectedin the brand new address with anew private key(which you should now also keepVERY private!) By emptying the addressbeforeyou import it’s private key youeliminatethe risk of theft entirely. One cannot take from analready emptyjar. It should also be noted toNEVERuse the imported address again as an addedsafety precaution*!*
👏👏👏 DONE! ENJOY YOUR FREE MONEY! 👏👏👏
How Much RNG Will I Receive?
Litecoin Cash holders will receive the highest claim ratio (5000 LCC = 1 RNG) as the LCC team are the ones responsible for creating Ring and wanted to extend a heart-felt thank you to the LCC community for their years of support. All other coins will be based on a 1:1 ratio with the value of Bitcoin at the time of the fork. This of course means 1 BTC = 1 RNG. For DASH and DOGE, however, their BTC market prices will determine their reward ratios. (For example ifDASHis trading at0.015 BTCeach, then eachDASHcoin will net you a reward of0.015 RNGto match.) Of course you don't need whole coins to claim, partial decimals work just fine!
What Value Will RNG Have?
That, my friends, is entirely up to the markets. No one in the history of crypto has had a perfect track record of price predictions so I'm not even going to try here. I will say, though, having gotten to play with their Testnet a bit so far that I am very impressed with the new Proof-of-Play method and how they have initially implemented it. It bodes very good things for the future of their project and this coin so I personally would expect its value to hold and most likely rise steadily as more people become aware of this groundbreaking new tech and it's potential to expand outward!
Is Litecoin Cash Still Going To Exist?
Absolutely! At least, from what I can gather. LCC has it's own purposes and will continue to be developed on. Ring is not meant to be a replacement or upgrade of any kind to Litecoin Cash. It is an entirely different proofing algorithm and a different mission statement altogether. It's more so meant to help expose the amazing new technologies developed on the LCC blockchain to a wider audience beyond simply its own fan base. If anything it'll act a sister chain that can help expose more folks to LCC in the future!
Disclaimer
While I am a moderator for the Litecoin Cash Discord server, I am writing this from an independent point of view as an educated crypto enthusiast with a passion for helping others navigate these waters. Having been an initial forker and third party developer on top of LCC myself, I feel I have some valuable insight into the direction the team is taking and I wanted to offer some sound advice for the upcomingRing forkbefore the FUD gets caked on too thick. I know a lot of people get scared easily in crypto because of the rampant scamming that goes on but I've watched this team work their asses off for two years to get out from under the stain of Charlie Lee's very biased, uneducated "its a scam" tweet which was endlessly parroted throughout the Litecoin community with nothing but blind party loyalty and no due diligence. The LCC folks arekind, wonderful hard-working peoplewith big hearts and ambition and they have actually developed aunique proofing methodologythat is likely going to impress a lot of people! So before you go jumping on the "it's just another shitcoin" bandwagon please stop and take a real hard look at bothLitecoin Cash (LCC)andRing (RNG):two viable projects with something to bring to the table! If nothing else, hey, just claim your new coins and dump them off for some free money. You literally cannot lose if youPRACTICE SAFE FORKING!!! Good luck, cryptonauts! =A=
Brainwallet Generator. If you have trust issues with third-party services (BTC.com, Blockchain.com, BitGo.com, Coinbase.com, etc) securing your Bitcoin, Altcoin, or other Cryptocurrency, you will want a Brainwallet – the most affordable and secure solution today. There are light weight SPV wallets, mobile and hardware wallets but nothing comes close like operating a core wallet. But the huge drawback of running a core wallet is its disk space and bandwidth requirements. The current Bitcoin blockchain size is more than 200 GB which is immense and not everyone is ready to allocate such a huge space for ... 4. Types of Wallets. There are two main types of Bitcoin wallets – cold storage, and hot wallets. Cold storage: The secure way to hold Bitcoin. Cold storage (or cold wallets) refers to any type of wallet that is detached from an Internet connection and therefore cannot be hacked remotely. Manage personal, business, and testnet wallets easily, all without leaving the app. Copay uses hierarchical-deterministic (HD) wallets, allowing for secure in-app wallet generation and backup. Copay is one of the first bitcoin wallets to support the full Bitcoin Payment Protocol (BIP 0070-0073). Run bitcoin-qt or bitcoind with the -testnet flag to use the testnet (or put testnet=1 in the bitcoin.conf file). There have been three generations of testnet. Testnet2 was just the first testnet reset with a different genesis block, because people were starting to trade testnet coins for real money. Testnet3 is the current test network. It was ...
Intro to Chemistry, Basic Concepts - Periodic Table, Elements, Metric System & Unit Conversion - Duration: 3:01:41. The Organic Chemistry Tutor Recommended for you NEW CHANNEL: https://www.youtube.com/channel/UCH9HlTrjyLmLRS0iE1P4rrg ----- Rich Dad Poor Dad: https://amzn.to/3cKJ4Ia C... How to Setup a Electrum Bitcoin Wallet on Testnet & Free Bitcoin Faucet PIAIC Description: Electrum Wallet Download : https://electrum.org/#download Free T... In today's video I go over creating an asset on the Ravencoin testnet. ... Bitcoin with your credit card here: https://goo.gl/m1pXxJ Secure your Bitcoin with the Ledger Nano S Hardware Wallet ... How to activate your bitcoin core testnet to be used as a temporary datastore with Apertus 0.3. Applies to Windows 10 and most cryptocurrencies derived from bitcoin. Category
![[TUTORIAL] -- How to SAFELY Claim New RNG Coins Using Your Private Keys](https://b.thumbs.redditmedia.com/JzEOiXZoA2Agth8r0O1MzREcJRtMQ9btzEnyJoXfQEs.jpg "[TUTORIAL] -- How to SAFELY Claim New RNG Coins Using Your Private Keys")
![[TUTORIAL] -- How to SAFELY Claim New RNG Coins Using Your LCC Private Keys](https://a.thumbs.redditmedia.com/oivCcEythly1Sx_AULOTCAs0sdIlL3NfUBusjYMAHZ0.jpg "[TUTORIAL] -- How to SAFELY Claim New RNG Coins Using Your LCC Private Keys")
