Coinbase – Buy & Sell Bitcoin, Ethereum, and more with trust

Feather - free, open-source Monero desktop wallet releasing soon™

For the past year tobtoht and I have been working on the foundations of a new Monero desktop GUI called Feather for Mac OS and Linux platforms (Windows tentative) using Qt5, libwallet, QtWidgets.
The goal of this new wallet is to provide a practical, robust and easy-to-use Monero wallet for every day use. It aims to be beginner friendly, but should also cater to the needs of experienced Monero users with the addition of advanced features like coin control and multisig.
Feather's user interface is inspired by Bitcoin's Electrum wallet, but adapted to fit Monero. Feather is not a fork of Electrum, all of the UI code was written from scratch in C++ / QtWidgets.
Development began in the summer of 2019. We estimate to release a beta version in November or December.

Video preview

https://www.youtube.com/watch?v=tylbteVtwrw (watch fullscreen)

Why

Our primary motivation is to create a wallet that we ourselves would want to use and recommend to friends. There aren't many options when it comes to non-custodial Monero desktop wallets. The CLI is an excellent tool for power-users, but is simply not an option for users that are not familiar with with the terminal. The GUI has a slick user interface, but is demanding on system resources due the use of Qt Quick.
Instead we've taken inspiration from Bitcoin's Electrum and started working on the most basic looking Monero desktop wallet one can imagine. We've gotten rid of a lot of functionality, but also added new functionality. Just focussing on the basics results in a clean, robust, and beginner proof wallet.

Privacy

In an effort to mitigate unintentional off-chain linking, we have made it harder to reuse addresses by automatically hiding used subaddresses. We find that the primary address leads uninformed users to believe that it is somehow functionally incompatible with subaddresses, or that funds sent to subaddresses can not be spent together. To encourage the use of subaddresses the primary address is hidden by default, and only used for change and coinbase outputs.
Our wallet supports advanced coin control features like freeze/thaw and sweeping a single output. In the future we may add manual transaction input selection.
There is no need to manually setup Tor to protect your traffic, Feather comes bundled with Tor. By default all traffic is routed through Tor with the exception of traffic between wallet and daemon. Wallet synchronization over Tor takes substantially longer than over clearnet, but you can optionally enable to connect to remote nodes over Tor. If your machine already has a Tor daemon running Feather can use the system daemon when instructed.
Just like in the official GUI, Feather essentially has 2 modes of connecting to the Monero network. You either host your node somewhere (localhost/LAN/internet) or we'll provide you one from a list of trusted, stable, community hosted remote nodes (like Cake Wallet). If Feather detects that it's running on Tails or Whonix it will automatically connect to a random .onion remote node.

Performance

Feather is built with Qt Widgets, providing native looks and performance. In a recent test™ a wallet with 10k+ transactions only consumed 200 MB ram (before optimizations). In comparison, the official GUI uses 400 MB before a wallet is opened.
GPU power is plenty nowadays so this hardly a problem, however, we are serious about providing an user interface that feels snappy to use. The application itself starts within 1-2 seconds on most machines (Bitcoin's Electrum is more like 4-5 seconds due to their usage of PyQt).

User experience

We have implemented Tevador's 14 word seed scheme with embedded restore height. The same function is used to derive the private view key from the private spendkey, therefore it is possible to convert the 14 word seed into a standard 25 word seed in case you want to restore the wallet using the official wallet software.
Feather connects to a websocket server over Tor to obtain miscellaneous data such as: price information, a list CCS proposals, posts on /Monero, the most recent blockheight, a list of community hosted nodes and the latest version of Feather.
The websocket server itself is open-source and self-hostable. By default Feather will connect to a server hosted by the project maintainers. The websocket connection can be disabled completely, but some functionality will be disabled/broken.
Our target audience are users who want to use Monero without too many issues and we've designed the wallet as such, with lots of convenience features, while routing it all over Tor in the background.
The native look of the application should feel familair to users as it behaves like any other program that runs on their computer. Added benefit for future contributors/developers is that it's very fast to implement/test UI components by borrowing from QtWidget's vast library. This in contrast with the Monero GUI, which uses custom QML components - a tricky and time consuming rendereframework more suited for large teams to create electron-like applications.

Additional information

Proposal

Work started early summer 2019. We still have some features to finish, prepare CI/CD, etc. As such we expect an alpha or beta release in December 2020. For this we would like the community's approval to allow the milestones defined in GUI CCS to be used for the remainder of this project, paid in full - we can use the support. Consequently all code will be licensed under the Monero Project and features/changes to libwallet or wallet2 will be committed to upstream (Monero GUI/core). Future development and releases will be maintained by dsc__ and tobtoht.

Beta testing

Idle in #feather on irc.oftc.net if you want to help beta testing in a month or so. You will need Linux, as this is our primary platform for developing the application.
Please let us know what you think in the comments. We're open to suggestions/feature requests/brainfarts.
submitted by dsc__ to Monero [link] [comments]

Groestlcoin 6th Anniversary Release

Introduction

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.

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

Other Linux

http://groestlcoin.org/forum/index.php?topic=97.0

Download

Download the Windows Installer (64 bit) here
Download the Windows Installer (32 bit) here
Download the Windows binaries (64 bit) here
Download the Windows binaries (32 bit) here
Download the OSX Installer here
Download the OSX binaries here
Download the Linux binaries (64 bit) here
Download the Linux binaries (32 bit) here
Download the ARM Linux binaries (64 bit) here
Download the ARM Linux binaries (32 bit) here

Source

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

Download

iOS
Android

Source

ALL NEW! – HODL GRS Android Wallet

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

Download

Main Release (Main Net)
Testnet Release

Source

ALL NEW! – GroestlcoinSeed Savior

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

Live Version (Not Recommended)

https://www.groestlcoin.org/recovery/

Download

https://github.com/Groestlcoin/mnemonic-recovery/archive/master.zip

Source

ALL NEW! – Vanity Search Vanity Address Generator

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

Usage

https://github.com/Groestlcoin/VanitySearch#usage

Download

Source

ALL NEW! – Groestlcoin EasyVanity 2020

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

Download

Source

Remastered! – Groestlcoin WPF Desktop Wallet (v2.19.0.18)

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

Remastered Improvements

Download

Source

ALL NEW! – BIP39 Key Tool

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

Download

Windows
Linux :
 pip3 install -r requirements.txt python3 bip39\_gui.py 

Source

ALL NEW! – Electrum Personal Server

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

Download

Windows
Linux / OSX (Instructions)

Source

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

Download

Main Net
Main Net (FDroid)
Test Net

Source

UPDATED – Groestlcoin Sentinel 3.5.06 (Android)

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.

Changes

Download

Source

UPDATED – P2Pool Test Net

Changes

Download

Pre-Hosted Testnet P2Pool is available via http://testp2pool.groestlcoin.org:21330/static/

Source

submitted by Yokomoko_Saleen to groestlcoin [link] [comments]

[TUTORIAL] -- How to SAFELY Claim New RNG Coins Using Your Private Keys

[TUTORIAL] -- How to SAFELY Claim New RNG Coins Using Your Private Keys

https://preview.redd.it/u4x1o4p37zc41.png?width=700&format=png&auto=webp&s=01d1ff52c0b7fc1c9ae5bb4f161979ad1f4bb559
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 a small amount of personal education you 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 things easier on yourself, you can optionally collect your original coins into as few addresses as possible BEFORE the snapshot. Doing so reduces the number of keys you will need to empty and import later. It’s just less 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 —
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 the only way to 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 to prove ownership of your snapshotted address balance plus use its empty key to then claim your new coins thus keeping your original coins completely protected in the brand new address with a new private key (which you should now also keep VERY private!)
By emptying the address before you import it’s private key you eliminate the risk of theft entirely. One cannot take from an already empty jar. It should also be noted to NEVER use the imported address again as an added safety 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 if DASH is trading at 0.015 BTC each, then each DASH coin will net you a reward of 0.015 RNG to 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 upcoming Ring fork before 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 are kind, wonderful hard-working people with big hearts and ambition and they have actually developed a unique proofing methodology that 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 both Litecoin Cash (LCC) and Ring (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 you PRACTICE SAFE FORKING!!!
Good luck, cryptonauts!
=A=
submitted by auscoine to RingCoin [link] [comments]

[TUTORIAL] -- How to SAFELY Claim New RNG Coins Using Your LCC Private Keys

[TUTORIAL] -- How to SAFELY Claim New RNG Coins Using Your LCC Private Keys

https://preview.redd.it/9csw52aw30d41.png?width=700&format=png&auto=webp&s=53ceb329c9772d7f0abbcc56b44ba405e34dd8a8
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 a small amount of personal education you 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 things easier on yourself, you can optionally collect your original coins into as few addresses as possible BEFORE the snapshot. Doing so reduces the number of keys you will need to empty and import later. It’s just less 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 the only way to 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 to prove ownership of your snapshotted address balance plus use its empty key to then claim your new coins thus keeping your original coins completely protected in the brand new address with a new private key (which you should now also keep VERY private!)
By emptying the address before you import it’s private key you eliminate the risk of theft entirely. One cannot take from an already empty jar. It should also be noted to NEVER use the imported address again as an added safety 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 if DASH is trading at 0.015 BTC each, then each DASH coin will net you a reward of 0.015 RNG to 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 upcoming Ring fork before 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 are kind, wonderful hard-working people with big hearts and ambition and they have actually developed a unique proofing methodology that 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 both Litecoin Cash (LCC) and Ring (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 you PRACTICE SAFE FORKING!!!
Good luck, cryptonauts!
=A=
submitted by auscoine to LCCofficial [link] [comments]

Transcript of Developer Meeting in Discord - March 29, 2019

Pho3nix Monk3y03/29/2019
Is this unlocked?
oh cool. yes it is
Guess we need an admin to unlock it. Some of our devs cant type in here yet.
@shiggidy @traysi ★★★★★ Can yall unlock this channel?
traysi ★★★★★03/29/2019
Should be open now
bhorn03/29/2019
open!
GhostDogsGhost03/29/2019
heya!
SamzOnline [w1ne]03/29/2019
Woot
theking03/29/2019
Glad to be here.
traysi ★★★★★03/29/2019
@Jeroz can you type now?
Jeroz03/29/2019
Works now
ty
Pho3nix Monk3y03/29/2019
Great. Didn't really have an agenda for this meeting I'm told. Can open it up? Anyone have anything to start?
Bianca_NL03/29/2019
YaY
GhostDogsGhost03/29/2019
testnet voting on messaging bip?
Pho3nix Monk3y03/29/2019
I like it.
@GhostDogsGhost You might be the main "answerer of questions" for this. Not sure where @[Dev-Happy] Blondfrogs is.
GhostDogsGhost03/29/2019
anyone know if it's passed? if and when it'd be great to get some usage
Vincent03/29/2019
all good @traysi ★★★★★
Jeroz03/29/2019
Messaging is active on testnet now. The vote passed.
traysi ★★★★★03/29/2019
I'll try to clean up the permissions for this channel to make it simpler for future meetings.
Jeroz03/29/2019
There is no GUI yet to test it.
GhostDogsGhost03/29/2019
sweet -- yeah just rpc for now
[Dev-Happy] Blondfrogs03/29/2019
here
Pho3nix Monk3y03/29/2019
yay
[Dev-Happy] Blondfrogs03/29/2019
So, for messaging. There is not GUI, we really want to test the protocol which you can use fully through the rpc console.
We understand that this limits the number of users that will want to do testing but we wanted to get it out there asap to find bugs
Jeroz03/29/2019
Is there list of commands / little guide on how to get started with them in the console?
[Dev-Happy] Blondfrogs03/29/2019
Also, we wanted to let everyone know that we are going to try and get messaging protocol and restricted assets on mainnet at the same time. This means that the release for messaging might be delayed by a couple weeks. The devs are working really hard to make this happen and hope that the community is willing to wait a little longer for mainnet messaging.
There are commands like sendmessage listmessages and subscribe rpc calls yes
Jeroz03/29/2019
That would mean 1 hardfork instead of 2 right?
[Dev-Happy] Blondfrogs03/29/2019
Exactly @Jeroz
[Master] Roshii03/29/2019
Hello!
[Dev-Happy] Blondfrogs03/29/2019
Also, the Qt for messaging wont be released until after the hardfork, but the Qt for messaging and restricted assets would be in the same release.
S1LVA | GetRavencoin.org03/29/2019
Hello! Thanks for holding this meeting.
Jeroz03/29/2019
Will dividends also be included to that? @WhaleStreet (BW) (not sure if you are here)
[Dev-Happy] Blondfrogs03/29/2019
Dividends can be released at anytime it is completed as it doesn't require a hardfork
Jeroz03/29/2019
I meant the GUI update
S1LVA | GetRavencoin.org03/29/2019
For restricted assets, will owners of !uniquename have a grace period to claim $uniquename ?
[Dev-Happy] Blondfrogs03/29/2019
I am not sure on the GUI for dividends.
We are still figuring out if we are going to allow for a grave period or not. I think we are leading to the answer of Yes there will be a grace period.
but we aren't sure yet
SamzOnline [w1ne]03/29/2019
I've been studying and out of the loop of the RVN scene for a long time - is there any chance of someone updating me on what y'all talking about?
Pho3nix Monk3y03/29/2019
We have also been going through and cleaning up issues in GitHub. Tried to clean up tags in there as well. We will probably start going though those on a weekly ->monthly basis to stay ahead of things.
Vincent03/29/2019
community seens to agree !ASSET has exclsuvie on $ASSET
GhostDogsGhost03/29/2019
Silva -- that's open for discussion -- I think the general sentiment is that there should be some preference given to current asset owners
[Dev-Happy] Blondfrogs03/29/2019
@SamzOnline [w1ne] We are talking about the roadmap and how the development of the new features are coming along.
SamzOnline [w1ne]03/29/2019
Lovely many thanks
Vincent03/29/2019
what is the justification on only a grace period?
S1LVA | GetRavencoin.org03/29/2019
Is it possible to reissue a !ownership as a $ownership?
Jeroz03/29/2019
@SamzOnline [w1ne]
https://medium.com/@tronblack/ravencoin-tags-and-restricted-assets-84fe3070a226
https://medium.com/@tronblack/ravencoin-kaaawww-2f72077aece
[Dev-Happy] Blondfrogs03/29/2019
@Vincent I don't think is has exclusive rights. More like a first right of refusal for a couple months
Synicide03/29/2019
agree there should be some kind of grace period, or users that originally registered those assets will feel shafted
Vincent03/29/2019
but what is that justification?
if you are building Applein ur garage, you may need a few yrs to go public
S1LVA | GetRavencoin.org03/29/2019
Issue being assets will cease to be unique with two different types about
[Dev-Happy] Blondfrogs03/29/2019
True.
We aren't sure on what approach will be taken yet
Synicide03/29/2019
should regular and restricted assets share the same 'uniqueness of naming'?
[Dev-Happy] Blondfrogs03/29/2019
Please the community let us know what you think is fair.
This topic will 100% need to be discussed a lot
Vincent03/29/2019
when it was announced, there was a lot of discussion; most seemed to agree
SamzOnline [w1ne]03/29/2019
@Jeroz Many thanks
[Dev-Happy] Blondfrogs03/29/2019
If the consensus is that we shouldn't allow for ASSET! and $ASSET to be issued by different people then we will need to make sure that is the right approach. The code hasn't been written yet.
GhostDogsGhost03/29/2019
Some of this will depend on what we end up pricing the $ASSETS at (burn for issuance)..
Vincent03/29/2019
prcing shouldnt matter imo
S1LVA | GetRavencoin.org03/29/2019
We need to determine how important unique asset names are, for varying types.
Vincent03/29/2019
should be the owner of the asset name
[Dev-Happy] Blondfrogs03/29/2019
@S1LVA | GetRavencoin.org Exactly
push | ravenland.org03/29/2019
hey all, sorry im late :thumbsup:
[Dev-Happy] Blondfrogs03/29/2019
Howdy
Synicide03/29/2019
If someone registers !company123, and starts building a platform for themselves, seems they should be given an option to convert to $company123, and shouldnt have to worry about another party creating $company123
[Dev-Happy] Blondfrogs03/29/2019
They will be given that option
Vincent03/29/2019
indefinately
[Dev-Happy] Blondfrogs03/29/2019
the question is, is that option going to exist for forever, or maybe only 4 months
Vincent03/29/2019
then the worry still exists
Rikki RATTOE Sr. SEC Impresantor03/29/2019
I definitely vote for ! And $ to only be issued by the same people
Synicide03/29/2019
lets say they choose not to, can someone else create $company123? Or is that unqiue name shared?
S1LVA | GetRavencoin.org03/29/2019
I believe, ideally, a reissuance option would be available at anytime from !ownership
[Dev-Happy] Blondfrogs03/29/2019
@Synicide That decision hasn't been made yet
theking03/29/2019
@[Dev-Happy] Blondfrogs I do agree that releasing both messaging and restricted assets at same time makes sense so there is only one hard fork. What is the current thinking on tentative timeline before they would both be on main net?
push | ravenland.org03/29/2019
im excited about this memo indication, its useful because it means a buyer of an asset sending rvn can indicate the 'return address' without the 'seller of the asset receiving ravencoin' having to transverse the full vin/vout chain to obtain the source address to dispatch asset to. Is there a timeline for this feature or any documentation on it @[Dev-Happy] Blondfrogs ?
Synicide03/29/2019
my 2 cents, they should be a shared pool of unique names. The door is opened for scammers galore if it isnt.
[Dev-Happy] Blondfrogs03/29/2019
@theking A couple months atleast.
To make sure it is tested on testnet for long enough
theking03/29/2019
That makes perfect sense!
[Dev-Happy] Blondfrogs03/29/2019
@push | ravenland.org It will be on mainnet as soon as it and restricted assets are tested. Is the goal
push | ravenland.org03/29/2019
excellent, i look forward to it
Chill03/29/2019
Thank you for taking the time to bring up the ! and $ ownership issue. It's of extreme importance imo
push | ravenland.org03/29/2019
its gods work your doing there
bitnaive03/29/2019
yeah it seems like any modifiers to the original !NAME should belong to !NAME
DirkDiggler (RVN ded)03/29/2019
I would like to voice concern over the idea of the "grace period".... The idea of a UNIQUE asset name is key to our success. Many of us jumped on names we wanted. This doesn't feel right to need to have yet another name floating around if it's not controlled by the !OWNERSHIP token
S1LVA | GetRavencoin.org03/29/2019
@Chill NP :p
Rikki RATTOE Sr. SEC Impresantor03/29/2019
Yes please on only 1 hard fork
Chill03/29/2019
unique is unique. I have 510 of them!
Synicide03/29/2019
@DirkDiggler (RVN ded) grace peroid wont matter if the naming pool is shared for uniqueness
[Dev-Happy] Blondfrogs03/29/2019
So, If I own GOOGLE!, and I don't want $GOOGLE, no one should be allowed to own it?
DirkDiggler (RVN ded)03/29/2019
exactly
S1LVA | GetRavencoin.org03/29/2019
@[Dev-Happy] Blondfrogs Ideally, yes
bhorn03/29/2019
that feels right to me
Jeroz03/29/2019
yes
SamzOnline [w1ne]03/29/2019
Interesting
DirkDiggler (RVN ded)03/29/2019
yes
Rikki RATTOE Sr. SEC Impresantor03/29/2019
@[Dev-Happy] Blondfrogs I'm good w that
Synicide03/29/2019
that makes the most sense to me. As said, opens the door to scammers if not
Rikki RATTOE Sr. SEC Impresantor03/29/2019
Would add extra value to the ownership token as well
S1LVA | GetRavencoin.org03/29/2019
If more power is given to !ownership(changing type), more value is added to said asset, by way of design and ability
Vincent03/29/2019
and if you want to covert your assets to restricted yrs from now you will have a logistic nightmare if you have a bunch of owners
[Dev-Happy] Blondfrogs03/29/2019
I feel like, if we give people the option to register the restricted asset $ and they don't want it, that it is only fair that it is up for grabs
bitnaive03/29/2019
maybe no one else should be allowed to issue it but it can be transferred
Vincent03/29/2019
why?
Chill03/29/2019
I really don't think that's fair, to be honest
S1LVA | GetRavencoin.org03/29/2019
@[Dev-Happy] Blondfrogs Unique names are lost, in that case.
And in that way, !ownership loses value by not having the ability to change, if need be
Rikki RATTOE Sr. SEC Impresantor03/29/2019
Yeah I'd rather see the one name issued only forever
bitnaive03/29/2019
that way, if some one wants it. the can contact the owner for it.
[Dev-Happy] Blondfrogs03/29/2019
I think restricted assets have a different use case than regular assets, and they can be frozen.
Vincent03/29/2019
i can buy ravenland and revent push from moving forward with is project (after grace)
DirkDiggler (RVN ded)03/29/2019
seems like from a "code" perspective... the idea of 2 different (but similar names) would be a nightmare as well
Jeroz03/29/2019
Ideally give reissuable the extra option of making it restricted in my mind. I have mixed feelings about tokens traveling around that have the same asset name but are a different type.
Vincent03/29/2019
all his logos would have to change to his new name
S1LVA | GetRavencoin.org03/29/2019
They not have them remain one in the same? With the ability to change to restricted, should they have to. Though reissuance?
[Dev-Happy] Blondfrogs03/29/2019
@Vincent That is why push would have plenty of time to pick up the ravenland restricted asset if he wanted it
Rikki RATTOE Sr. SEC Impresantor03/29/2019
One of our selling points over ETH is that ETH can issue a bunch of the same named assets as long as the contract address is different
Vincent03/29/2019
bbut who says what is enough time
i may need yrs
bhorn03/29/2019
the extra cost could be onerous as well
Chill03/29/2019
when the asset layer was launched, it was billed as being unique names. Be careful in changing this, please.
[Dev-Happy] Blondfrogs03/29/2019
True, that amount of time isn't determined yet, if this is the route that is taken
bhorn03/29/2019
some have many many many assets
Rikki RATTOE Sr. SEC Impresantor03/29/2019
RVN, u issue that name once, it can never be duplicated
DirkDiggler (RVN ded)03/29/2019
where as having just another sub asset type ($RESTRICTED) falls under the same hierarchy already defined
bhorn03/29/2019
and the RVN is not as cheaply replaced
[Dev-Happy] Blondfrogs03/29/2019
@Chill Not changing that, just talking about the next asset usecase and how it could be coded is all
Rikki RATTOE Sr. SEC Impresantor03/29/2019
What kind of burn costs are we thinking w issuing restricted assets?
Synicide03/29/2019
@[Dev-Happy] Blondfrogs what if push decides not to, then someone else registers it for malicious intent with the same name? Surely the person who built their company on chain doesnt want another token of their company name out there
Vincent03/29/2019
@[Dev-Happy] Blondfrogs you seem to be the only one fighting for the garce period
[Dev-Happy] Blondfrogs03/29/2019
@Rikki RATTOE Sr. SEC Impresantor Not sure yet, going to be more than regular issuanace is the thought.
Rikki RATTOE Sr. SEC Impresantor03/29/2019
Agreed
S1LVA | GetRavencoin.org03/29/2019
@Vincent Simply bringing it into conversation, no harm
[Dev-Happy] Blondfrogs03/29/2019
@Vincent Not fighting, just keeping an open mind. I just code it, I am not the one making the decision.
push | ravenland.org03/29/2019
hey this is a bit of a random question but i get a lot of subassets send to me, what about wildcard sending via the wallet? like if i wanted to send RAVENLAND/* to an address
Vincent03/29/2019
true but just showing what the concesous is
[Dev-Happy] Blondfrogs03/29/2019
@push | ravenland.org Create a request in the issues on github for extra functionality
push | ravenland.org03/29/2019
:thumbsup:
will do mate
Synicide03/29/2019
seems if ! and $ arent shared unique, then companies will have to register both just to protect themselves
Rikki RATTOE Sr. SEC Impresantor03/29/2019
How about a unique asset w re-issuable IPFS?
S1LVA | GetRavencoin.org03/29/2019
We should be giving more power to !ownership by allowing it the ability to change to $ - Not giving less power to !ownership by duplicating unique names.
Rikki RATTOE Sr. SEC Impresantor03/29/2019
GUNCERT provided a valid use case IMO for unique w re-issuable IPFS
[Dev-Happy] Blondfrogs03/29/2019
@Vincent Sure I get that.
Sevvy (not worried til 500sats)03/29/2019
Agrees
If this is a possibility, to give the restricted assets to those who own the normal ones, it ought to be done
[Dev-Happy] Blondfrogs03/29/2019
@Rikki RATTOE Sr. SEC Impresantor Looking in on how to do that. The request is on github just don't have the time to implement it yet.
restricted assets, will have to be issued. and the corresponding amount of rvn will be burned for them
push | ravenland.org03/29/2019
it'd be nice to see a ravencoin network swarm, us and mango farms are doing something with that so if anyone else wants to get involved, i think its a worthwhile thing to build the power of the ravencoin ipfs hash network to keep them hashes alive
Sevvy (not worried til 500sats)03/29/2019
Yikes
Ah well
push | ravenland.org03/29/2019
i wrote a programmatic script to scrape all the ipfs files, so i can probably runa simple enough shellscript to ipfs add pin everything from chain
Vincent03/29/2019
plus ravenland sent me a bunch of tokens...they will be worthless now!!! :sunglasses:
push | ravenland.org03/29/2019
:joy:
vincent
one day tho eh
Chill03/29/2019
my 250,000 RVN that were spent on RVN assets are feeling pretty weak at the moment
[Dev-Happy] Blondfrogs03/29/2019
@Vincent haha ravenland assets are still assets. They just don't have the ability to freeze then and stop you from trading them
DirkDiggler (RVN ded)03/29/2019
you got to have one ring to rule them all... the Unique Ownership Token does that
SamzOnline [w1ne]03/29/2019
@Chill That puts my 80 to shame!
[Dev-Happy] Blondfrogs03/29/2019
@Chill Like I said, no decision has been made yet.
Vincent03/29/2019
@[Dev-Happy] Blondfrogs just playing with that one
[Dev-Happy] Blondfrogs03/29/2019
@Vincent Yeah, I understand
S1LVA | GetRavencoin.org03/29/2019
Changing gears alittle, Has any further thought been put into privacy?
push | ravenland.org03/29/2019
a tor network with proxychains could be effectively used to privatize a node
Jeroz03/29/2019
Seems that we need to continue discussions about the asset naming and make a write up about the proposals.
I have a different question:
About metadata and transactions. Tron mentioned that it will be possible to attach metadata to every transaction. It was unclear to me whether he meant every messaging transaction or every regular RVN/Asset transaction.
push | ravenland.org03/29/2019
ive been looking into this a little bit
Synicide03/29/2019
@S1LVA | GetRavencoin.org been wondering that too, and if restricted assets for KYC/AML NEED to be trackable
[Dev-Happy] Blondfrogs03/29/2019
@S1LVA | GetRavencoin.org Privacy isn't the main thing ravencoin wants right now. We need to be able to send and trade assets with visibility of amounts and the asset names. Once the main core components are finished, we can start thinking about integration privacy.
push | ravenland.org03/29/2019
as i understand it tor could as a protocol be built into ravencoin itself and distroed as a private tor based connector or hardened in such a way not to leak dns or requests that are not 'tor' proxied .. but you could do this already with some modifications to most linux systems (without the need for a ravencoin release)
S1LVA | GetRavencoin.org03/29/2019
Understood
[Dev-Happy] Blondfrogs03/29/2019
@Jeroz With messaging, all asset transactions can contain a metadata field yes.
Jeroz03/29/2019
RVN too?
[Dev-Happy] Blondfrogs03/29/2019
Not RVN at this time, as that already exists with the OP_RETURN functionality of bitcoin
Jeroz03/29/2019
Yeah I was about to say
S1LVA | GetRavencoin.org03/29/2019
I dream of one day Ravencoin giving users the ability to protect themselves from state level actors looking to oversee transactions on chain.
[Master] Roshii03/29/2019
What's the subject?
[Dev-Happy] Blondfrogs03/29/2019
@S1LVA | GetRavencoin.org That would be amazing, however the dividends and voting require a public ledger in order to send
Synicide03/29/2019
@[Master] Roshii large one is if regular and restricted assets should share unique names, and/or if a grace peroid should be allowed for original owners to register restricted assets
[Dev-Happy] Blondfrogs03/29/2019
So we would need to figure out a way to have that info public and keep privacy
S1LVA | GetRavencoin.org03/29/2019
Agree'd
Synicide03/29/2019
that was my worry, that it HAS to be public for a lot of uses. Privacy would have to be optional
[Dev-Happy] Blondfrogs03/29/2019
ravencoin was built and is being built to support asset trading. Privacy is important but isn't currently the focus of the dev team.
Synicide03/29/2019
sounds good, focus on our roadmap and can research it more in the future
S1LVA | GetRavencoin.org03/29/2019
Privacy is one of the very lasts subjects brought up in the whitepaper, after all :wink:
Vincent03/29/2019
to bring up an old topic; assets that haven't been reissued, there was talk about lowering the decimal places to reissue; i know not important but if it needed to be in a hard fork; should it be looked at the add to th next?
[Dev-Happy] Blondfrogs03/29/2019
@Vincent I have found a way to do this, however it requires the reissuer to own all assets
Synicide03/29/2019
how would you determine the correct values if lowering decimals? rounding?
Rikki RATTOE Sr. SEC Impresantor03/29/2019
@[Dev-Happy] Blondfrogs Yes!
Vincent03/29/2019
correct
nice
Synicide03/29/2019
if they all own, I guess its a non-issue
[Dev-Happy] Blondfrogs03/29/2019
We aren't currently working on that, but I will try and get it into the hard fork release
Vincent03/29/2019
it would be a 1 time option, correct?
Rikki RATTOE Sr. SEC Impresantor03/29/2019
In that event too, ability to reduce total supply as well if u still own every asset created would also be an excellent Option to have
When 350? (350club)03/29/2019
Is Bruces worry about the security of Ravencoin a curent issue?
Chill03/29/2019
That seems to be the talk of the day
Zaab03/29/2019
Its just honesty
Sevvy (not worried til 500sats)03/29/2019
We know a 51% attack is cheap
[Dev-Happy] Blondfrogs03/29/2019
@Vincent Depends on if it meets requirements.
Sevvy (not worried til 500sats)03/29/2019
But reorg depth protection is good
Rikki RATTOE Sr. SEC Impresantor03/29/2019
Yes Ravencoin currently doesn't have the network security that Bitcoin does, and water is wet
push | ravenland.org03/29/2019
more full nodes is the answer to a stronger consensus and therefore a more securer network
Sevvy (not worried til 500sats)03/29/2019
Hmmm checks out
push | ravenland.org03/29/2019
:ThinkBlack:
Vincent03/29/2019
right i guess my question is one time at most?
Synicide03/29/2019
It feels like more than just honesty. The last 4 post in a row from the Ravencoin twitter have some type of FUD based around it. Its all you see on the first page when looking at it. Some of that stuff needs to be kept to his personal account
Sevvy (not worried til 500sats)03/29/2019
Probably not a development Question, what Bruce says on his own time. :persevere:
Rikki RATTOE Sr. SEC Impresantor03/29/2019
@Synicide Bruce don't wanna spend a fortune on restricted assets :yum:
Sevvy (not worried til 500sats)03/29/2019
I don't like it myself either though @Synicide
boatsandhoes03/29/2019
yeah the ravencoin twitter has been a bit..... not good to put it easy
Vincent03/29/2019
this is bruces baby...and fud should be taken lightly imo
[Dev-Happy] Blondfrogs03/29/2019
Bruce can say what he wants :_)
Chill03/29/2019
well, it is the unofficial official Twitter page, so it kind of does matter
[Dev-Happy] Blondfrogs03/29/2019
We have taken measures to make sure ravencoin is safe and to stop 51% attacks
Synicide03/29/2019
I agree on his personal account. When people look up this project on twitter, they dont need a full page of fud
push | ravenland.org03/29/2019
its not a very development orientated debate tho in fairness
Vincent03/29/2019
no news will stop a well designed code
S1LVA | GetRavencoin.org03/29/2019
Many new users are asking about IPFS integration. Is this still being researched?
When 350? (350club)03/29/2019
I only asked as it appeared Bruce was saying there is a current security vulnerability..
push | ravenland.org03/29/2019
@[Dev-Happy] Blondfrogs what can people do to help secure the ravencoin network into 2019 and in the future?
Rikki RATTOE Sr. SEC Impresantor03/29/2019
@When 350? (350club) Bruce doesn't code, he wouldn't know
boatsandhoes03/29/2019
sorry, got a late start on this meeting. is kyc stuff on the table for discussion today, or is that at a later meeting?
[Dev-Happy] Blondfrogs03/29/2019
@push | ravenland.org Looks at the PR's, make sure the code being added is well written and secure.
push | ravenland.org03/29/2019
sure thing
and run fullnodes right?
[Dev-Happy] Blondfrogs03/29/2019
Run nodes, and mine ravencoin!
haha
hashpower
push | ravenland.org03/29/2019
:thumbsup:
boatsandhoes03/29/2019
that part
Pho3nix Monk3y03/29/2019
Looks like its time.
Jeroz03/29/2019
Alright, I have to pick up my son. Thanks everyone!
Pho3nix Monk3y03/29/2019
Thanks all
Rikki RATTOE Sr. SEC Impresantor03/29/2019
Thx!
Vincent03/29/2019
:sunglasses:
push | ravenland.org03/29/2019
cheers again :thumbsup: keep up the good work :rvn_hop:
Chill03/29/2019
thanks for everyone's hard work
Synicide03/29/2019
great talks today, thanks guys
Pho3nix Monk3y03/29/2019
Can have an admin shut it down and move this over to another channel until next time.
[Dev-Happy] Blondfrogs03/29/2019
Thanks for voicing your concerns.
S1LVA | GetRavencoin.org03/29/2019
Thanks everyone
Pho3nix Monk3y03/29/2019
@traysi ★★★★★ can you lock it back?
traysi ★★★★★03/29/2019
The channel is locked now.
submitted by mrderrik to Ravencoin [link] [comments]

I recovered my lost Bitcoins!

Just thought I would give an update to this post. It’s related to the issue of change going to a different address that has been in contention lately, so figured it was relevant.
I managed to get my coins back today, and wow it feels good!
The cause of the missing coins was because I was making payments from the same wallet on two computers while they were syncing with the block chain. For whatever reason, a change address for a transaction went missing. I had tried many times to load different wallets and rescan the blockchain again and again and never had any luck. In the end I had a mess of different wallet files, 16 in total, none of which included the relevant address when loaded in Bitcoin-qt.
Well after the price went over $100 I figured I would have another crack at it and took a different approach to see if I could recover the coins.
I installed pywallet and did a dump of each wallet file that I had. I have never deleted a wallet file and this is what saved me.
I searched the dumped wallet files and in one of the files I found the address I was looking for! I assumed I must have missed this wallet so I loaded up Bitcoin with the relevant wallet and let it sync….
I was disappointed; the transactions as they loaded did not contain the change I had expected. But I had seen it in the dump of the wallet.dat it must be there!
I ran the following command within the Bitcoin console after unlocking the wallet.
Dumpprivkey  
My heart skipped a beat, it returned a key!
I then imported this key to a blockchain.info wallet using the import feature and my balance adjusted! I had recovered my missing Bitcoins! I then transferred them to my new secure wallet and the transaction confirmed, happiest day of my life.
Here are some things I have learned that should probably be common knowledge for anyone using Bitcoin.
Keep your Bitcoins safe everyone! Tips: 1LJtAE6FVa2u7oy6ENnpYorhnrwyymt6UL
Edit: formatting.
submitted by Beast_Man to Bitcoin [link] [comments]

How to setup a Dogecoin Vanity Address!

WHAT IS A DOGE VANITY ADDRESS
Vanity addresses are ones where you can choose what characters appear somewhere in the address. For example, DPie5ucpypDTUsgquc3ea2Meg6TwpW6mW1. All Doge addresses must start with D (capital) and the second character must be a capital if it is a letter (not all letters accepted, for example I O Y W are not allowed as the second character). You can also create letters or words at the end or even beginning of the address such as:
Letters that I have found valid as second characters are: 5 6 7 8 9 A B C D E F G H J K L M N P Q R S T U
HOW TO CREATE YOUR VERY OWN DOGE VANITY ADDRESS
HOW TO IMPORT YOUR NEW DOGE VANITY ADDRESS INTO YOUR DOGECOIN-QT WALLET
For MultiDoge, see here
<3 pie
submitted by PieCrafted to dogecoin [link] [comments]

Moving Bitcoins from Bitcoin Core client to thin client

So I haven't really touched my bitcoin in half a year or so. I want to move from the core client to a thin client now since my disk space is at a premium.
My bitcoin qt client hasn't been sync'd for half a year. Is my only choice to sync it, then send the funds to a thin wallet?
EDIT: Title should say Bitcoin-qt, I guess things changed since I've been away and things are called Bitcoin Core now. EDIT2: Exported the keys and sent the BTC to an Electrum wallet. Here's my steps in case anyone else needs it.
To export a private key from your bitcoin-qt client (bitcoin-0.8.6-win32 for me):
  1. launch your bitcoin client as usual, don't need to wait for block chain to sync
  2. Click Help > Debug Window > Console
  3. Console > walletpassphrase [your walletpassphrase here] [600 (timeout in sec)] (Unlocks your wallet for 600 sec)
  4. Console > dumpprivkey [receving ADDRESS] (this will return the private key, you can copy it now; ensure you clear your clipboard/history afterwards)
  5. Console > walletlock
submitted by thunder_cougar to Bitcoin [link] [comments]

[Guide] How to transfer your wallet from your computer to android.

I got tired of waiting and waiting for the whole blockchain to sync so I decided to move my dogecoins to my phone since the app does not need to download the whole chain. (Luckily there is a bounty for a electrum equivalent that will hopefully arrive soon.)
It is much much easier if you just transfer some funds to a new address on your android phone, but this tutorial is for those people like me who can't even get the dogecoin app to sync.
Surprisingly the whole process was very simple. Don't be put off by all the text or all the talk about security. I just want things to be accessible to beginners and to practice good habits. Root is not required.
Note: I am assuming you are using the official dogecoin-qt app and the Dogecoin Wallet app by langerhans.
Disclaimer: This will involve having your private key stored in plaintext. Proceed with caution and treat that file like you would a password. Do not share your private key with anyone.

Getting your private keys

A wallet comprises of public keys and private keys. Public keys are the addresses that you share, you can only use them for viewing. Private keys let you actually make transfers and are what makes you the owner of the wallet. Today we will be transferring those private keys to your phone. They will still be present on your computer unless you delete them, so keep that in mind security-wise.
You will have to replace everything in '<>' with your own values.
  1. Open the desktop app
  2. Open the wallet console by going to: Help -> Debug Window -> Console
  3. If your wallet is locked with a password, you'll need to unlock it by typing: "walletpassphrase 120".
  4. Get the private key for an address by typing: "dumpprivkey "
  5. Save the private key to a file.
  6. Repeat this for each address that you want to transfer over.
Please think about how much dogecoins you want to transfer over. Brarsh:
Do you need that much? What if you lose your device? Just like only keeping a small amount of cash in your wallet and most safe in the bank, only carry what you could conceivably use for that time without access to your main wallet.

Creating a backup file

Next we need to create a backup file so that we can import our addresses into the android app. The android app uses the same format for its backup files as MultiBit (A popular bitcoin app). A typical file looks like the following:
# KEEP YOUR PRIVATE KEYS SAFE! Anyone who can read this can spend your Bitcoins. Kwmxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 2013-06-22T18:36:35Z L1Sxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 2013-05-04T22:47:32Z Kxwxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 2013-05-08T00:58:28Z 
What we want to do is put our private keys in the following format: key date-of-address-creation, where the date is in the format YYYY-MM-DDTHH:MM:SSZ. Note the T and the Z. The android app needs the date so it knows how far back into the blockchain it needs to sync.
If you can't remember when you created the address, visit http://dogechain.info/address/YOURADDRESS and get the date of the earliest transaction. It says that the dates are approximate, so I'd just put 00:00:00 for the time.
You should now have a valid unencrypted backup of your wallet.

Importing the backup

  1. Transfer the backup to your android phone, placing it in your Download folder. It has to be put in the Download folder or else the dogecoin app won't find the backup. Make sure it has a name you'll remember later.
  2. Open the dogecoin app and click on: Back Up Keys -> Restore private keys. Click on the name of the backup and from the list that shows up, look for your backup, which should be unencrypted. Click Restore.
  3. Delete the backup in your Downloads folder. Remember, your private key is stored in plaintext in there, so it is important that you delete it. Delete the backup on your computer if it is there also.
  4. Wait for the app to sync completely. Your addresses will be added to the addresses that were already in the app, and your transactions should show up. If they do not, make sure that the date you put was correct and early enough.
  5. Go to Back up Keys > Back up private keys and create a backup. This time it will be encrypted with a password :). If you do not have a backup, you could lose all your coins if you lose your phone or the data on it.
  6. To the moon!

Terminology

I just got into dogecoin two days ago so correct me if any of this is wrong. Same thing with anything in the post :).
Blockchain/Dogechain: The blockchain is a ledger (record) of all the dogecoin transactions that have ever taken place. As of writing it is larger than 1GB in size. The blockchain is needed to find out how many funds you have in your wallet.
Wallet: A wallet is the digital equivalent of a real life wallet. It is where your money is tied to (It doesn't contain actual dogecoins, but someone else could explain that better than me). The wallet contains your addresses and your private keys, both which are needed to receive and send dogecoins respectively.

Sources

Getting your private key
Importing the key into the android app
submitted by cooper12 to dogecoin [link] [comments]

Facilitating Discussion of 0.9.0 FINAL of Bitcoin Core (aka Bitcoin QT)

To facilitate a detailed discussion of some of the finer points of this update, I added numbering to each bullet in release notes, and also posted it to RapGenius, where people can annotate it if they'd like.
I'm not a programmer, but I'm curious to hear what programmers and other people smarter than me have to say about all the new changes.
http://rapgenius.com/The-bitcoin-dev-team-bitcoin-090-final-lyrics
EDIT1 : Doh! Reddit detroyed all the formatting and now i'm on baby duty so can't fix it. EDIT 2: Nap time! Just fixed the formatting :)
---- 0.9.0 RELEASE NOTES ----
Part 1. RPC:
1.1 - New notion of 'conflicted' transactions, reported as confirmations: -1
1.2 - 'listreceivedbyaddress' now provides tx ids
1.3 - Add raw transaction hex to 'gettransaction' output
1.4 - Updated help and tests for 'getreceivedby(account|address)'
1.5 - In 'getblock', accept 2nd 'verbose' parameter, similar to getrawtransaction, but defaulting to 1 for backward compatibility
1.6 - Add 'verifychain', to verify chain database at runtime
1.7 - Add 'dumpwallet' and 'importwallet' RPCs
1.8 - 'keypoolrefill' gains optional size parameter
1.9 - Add 'getbestblockhash', to return tip of best chain
1.10 - Add 'chainwork' (the total work done by all blocks since the genesis block) to 'getblock' output
1.11 - Make RPC password resistant to timing attacks
1.12 - Clarify help messages and add examples
1.13 - Add 'getrawchangeaddress' call for raw transaction change destinations
1.14 - Reject insanely high fees by default in 'sendrawtransaction'
1.15 - Add RPC call 'decodescript' to decode a hex-encoded transaction script
1.16 - Make 'validateaddress' provide redeemScript
1.17 - Add 'getnetworkhashps' to get the calculated network hashrate
1.18 - New RPC 'ping' command to request ping, new 'pingtime' and 'pingwait' fields in 'getpeerinfo' output
1.19 - Adding new 'addrlocal' field to 'getpeerinfo' output
1.20 - Add verbose boolean to 'getrawmempool'
1.21 - Add rpc command 'getunconfirmedbalance' to obtain total unconfirmed balance
1.22 - Explicitly ensure that wallet is unlocked in importprivkey
1.23 - Add check for valid keys in importprivkey
Part 2. Command-line options:
2.1 - New option: -nospendzeroconfchange to never spend unconfirmed change outputs
2.2 - New option: -zapwallettxes to rebuild the wallet's transaction information
2.3 - Rename option '-tor' to '-onion' to better reflect what it does
2.4 - Add '-disablewallet' mode to let bitcoind run entirely without wallet (when built with wallet)
2.5 - Update default '-rpcsslciphers' to include TLSv1.2
2.6 - make '-logtimestamps' default on and rework help-message
2.7 - RPC client option: '-rpcwait', to wait for server start
2.8 - Remove '-logtodebugger'
2.9 - Allow -noserver with bitcoind
Part 3. Block-chain handling and storage:
3.1 - Update leveldb to 1.15
3.2 - Check for correct genesis (prevent cases where a datadir from the wrong network is accidentally loaded)
3.3 - Allow txindex to be removed and add a reindex dialog
3.4 - Log aborted block database rebuilds
3.5 - Store orphan blocks in serialized form, to save memory
3.6 - Limit the number of orphan blocks in memory to 750
3.7 - Fix non-standard disconnected transactions causing mempool orphans
3.8 - Add a new checkpoint at block 279,000
Part 4. Wallet:
4.1 - Bug fixes and new regression tests to correctly compute the balance of wallets containing double-spent (or mutated) transactions
4.2 - Store key creation time. Calculate whole-wallet birthday
4.3 - Optimize rescan to skip blocks prior to birthday
4.4 - Let user select wallet file with -wallet=foo.dat
4.5 - Consider generated coins mature at 101 instead of 120 blocks
4.6 - Improve wallet load time
4.7 - Don't count txins for priority to encourage sweeping
4.8 - Don't create empty transactions when reading a corrupted wallet
4.9 - Fix rescan to start from beginning after importprivkey
4.10 - Only create signatures with low S values
Part 5. Mining:
5.1 - Increase default -blockmaxsize/prioritysize to 750K/50K
5.2 - 'getblocktemplate' does not require a key to create a block template
5.3 - Mining code fee policy now matches relay fee policy
Part 6. Protocol and network:
6.1 - Drop the fee required to relay a transaction to 0.01mBTC per kilobyte
6.2 - Send tx relay flag with version
6.3 - New 'reject' P2P message (BIP 0061, see https://gist.github.com/gavinandresen/7079034 for draft)
6.4 - Dump addresses every 15 minutes instead of 10 seconds
6.5 - Relay OP_RETURN data TxOut as standard transaction type
6.6 - Remove CENT-output free transaction rule when relaying
6.7 - Lower maximum size for free transaction creation
6.8 - Send multiple inv messages if mempool.size > MAX_INV_SZ
6.9 - Split MIN_PROTO_VERSION into INIT_PROTO_VERSION and MIN_PEER_PROTO_VERSION
6.10 - Do not treat fFromMe transaction differently when broadcasting
6.11 - Process received messages one at a time without sleeping between messages
6.12 - Improve logging of failed connections
6.13 - Bump protocol version to 70002
6.14 - Add some additional logging to give extra network insight
6.15 - Added new DNS seed from bitcoinstats.com
Part 7. Validation:
7.1 - Log reason for non-standard transaction rejection
7.2 - Prune provably-unspendable outputs, and adapt consistency check for it
7.3 - Detect any sufficiently long fork and add a warning
7.4 - Call the -alertnotify script when we see a long or invalid fork
7.5 - Fix multi-block reorg transaction resurrection
7.6 - Reject non-canonically-encoded serialization sizes
7.7 - Reject dust amounts during validation
7.8 - Accept nLockTime transactions that finalize in the next block
Part 8. Build system:
8.1 - Switch to autotools-based build system
8.2 - Build without wallet by passing --disable-wallet to configure, this removes the BerkeleyDB dependency
8.3 - Upgrade gitian dependencies (libpng, libz, libupnpc, boost, openssl) to more recent versions
8.4 - Windows 64-bit build support
8.5 - Solaris compatibility fixes
8.6 - Check integrity of gitian input source tarballs
8.7 - Enable full GCC Stack-smashing protection for all OSes
Part 9. GUI:
9.1 - Switch to Qt 5.2.0 for Windows build
9.2 - Add payment request (BIP 0070) support
9.3 - Improve options dialog
9.4 - Show transaction fee in new send confirmation dialog
9.5 - Add total balance in overview page
9.6 - Allow user to choose data directory on first start, when data directory ismissing, or when the -choosedatadir option is passed
9.7 - Save and restore window positions
9.8 - Add vout index to transaction id in transactions details dialog
9.9 - Add network traffic graph in debug window
9.10 - Add open URI dialog
9.11 - Add Coin Control Features
9.12 - Improve receive coins workflow: make the 'Receive' tab into a form to request payments, and move historical address list functionality to File menu
9.13 - Rebrand to Bitcoin Core
9.14 - Move initialization/shutdown to a thread. This prevents "Not responding" messages during startup. Also show a window during shutdown
9.15 - Don't regenerate autostart link on every client startup
9.16 - Show and store message of normal bitcoin:URI
9.17 - Fix richtext detection hang issue on very old Qt versions
9.18 - OS X: Make use of the 10.8+ user notification center to display Growl-like notifications
9.19 - OS X: Added NSHighResolutionCapable flag to Info.plist for better font rendering on Retina displays
9.20 - OS X: Fix bitcoin-qt startup crash when clicking dock icon
9.21 - Linux: Fix Gnome bitcoin: URI handler
Part 10. Miscellaneous:
10.1 - Add Linux script (contrib/qos/tc.sh) to limit outgoing bandwidth
10.2 - Add '-regtest' mode, similar to testnet but private with instant block generation with 'setgenerate' RPC
10.3 - Add 'linearize.py' script to contrib, for creating bootstrap.dat
10.4 - Add separate bitcoin-cli client
submitted by WhiteyFisk to Bitcoin [link] [comments]

Bitcoin-QT 0.9 disponível para download

The Core Developers of Bitcoin released the 0.9.0 FINAL of Bitcoin Core (aka Bitcoin QT).
DOWNLOAD:
This is a Final Version, but its the same as 0.9.0rc3
Sources: https://github.com/bitcoin/bitcoin/releases http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.9.0/ https://bitcoin.org/bin/0.9.0/README.txt
Bitcoin Core version 0.9.0 is now available from:
https://bitcoin.org/bin/0.9.0/
This is a release candidate for a new major version. A major version brings both new features and bug fixes.
Please report bugs using the issue tracker at github:
https://github.com/bitcoin/bitcoin/issues

How to Upgrade

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), uninstall all earlier versions of Bitcoin, then run the installer (on Windows) or just copy over /Applications/Bitcoin-Qt (on Mac) or bitcoind/bitcoin-qt (on Linux).
If you are upgrading from version 0.7.2 or earlier, the first time you run 0.9.0 your blockchain files will be re-indexed, which will take anywhere from 30 minutes to several hours, depending on the speed of your machine.
On Windows, do not forget to uninstall all earlier versions of the Bitcoin client first, especially if you are switching to the 64-bit version.

Windows 64-bit installer

New in 0.9.0 is the Windows 64-bit version of the client. There have been frequent reports of users running out of virtual memory on 32-bit systems during the initial sync. Because of this it is recommended to install the 64-bit version if your system supports it.
NOTE: Release candidate 2 Windows binaries are not code-signed; use PGP and the SHA256SUMS.asc file to make sure your binaries are correct. In the final 0.9.0 release, Windows setup.exe binaries will be code-signed.

OSX 10.5 / 32-bit no longer supported

0.9.0 drops support for older Macs. The minimum requirements are now: * A 64-bit-capable CPU (see http://support.apple.com/kb/ht3696); * Mac OS 10.6 or later (see https://support.apple.com/kb/ht1633).

Downgrading warnings

The 'chainstate' for this release is not always compatible with previous releases, so if you run 0.9 and then decide to switch back to a 0.8.x release you might get a blockchain validation error when starting the old release (due to 'pruned outputs' being omitted from the index of unspent transaction outputs).
Running the old release with the -reindex option will rebuild the chainstate data structures and correct the problem.
Also, the first time you run a 0.8.x release on a 0.9 wallet it will rescan the blockchain for missing spent coins, which will take a long time (tens of minutes on a typical machine).

Rebranding to Bitcoin Core

To reduce confusion between Bitcoin-the-network and Bitcoin-the-software we have renamed the reference client to Bitcoin Core.

Autotools build system

For 0.9.0 we switched to an autotools-based build system instead of individual (q)makefiles.
Using the standard "./autogen.sh; ./configure; make" to build Bitcoin-Qt and bitcoind makes it easier for experienced open source developers to contribute to the project.
Be sure to check doc/build-*.md for your platform before building from source.

Bitcoin-cli

Another change in the 0.9 release is moving away from the bitcoind executable functioning both as a server and as a RPC client. The RPC client functionality ("tell the running bitcoin daemon to do THIS") was split into a separate executable, 'bitcoin-cli'. The RPC client code will eventually be removed from bitcoind, but will be kept for backwards compatibility for a release or two.

walletpassphrase RPC

The behavior of the walletpassphrase RPC when the wallet is already unlocked has changed between 0.8 and 0.9.
The 0.8 behavior of walletpassphrase is to fail when the wallet is already unlocked:
> walletpassphrase 1000 walletunlocktime = now + 1000 > walletpassphrase 10 Error: Wallet is already unlocked (old unlock time stays) 
The new behavior of walletpassphrase is to set a new unlock time overriding the old one:
> walletpassphrase 1000 walletunlocktime = now + 1000 > walletpassphrase 10 walletunlocktime = now + 10 (overriding the old unlock time) 

Transaction malleability-related fixes

This release contains a few fixes for transaction ID (TXID) malleability issues:

Transaction Fees

This release drops the default fee required to relay transactions across the network and for miners to consider the transaction in their blocks to 0.01mBTC per kilobyte.
Note that getting a transaction relayed across the network does NOT guarantee that the transaction will be accepted by a miner; by default, miners fill their blocks with 50 kilobytes of high-priority transactions, and then with 700 kilobytes of the highest-fee-per-kilobyte transactions.
The minimum relay/mining fee-per-kilobyte may be changed with the minrelaytxfee option. Note that previous releases incorrectly used the mintxfee setting to determine which low-priority transactions should be considered for inclusion in blocks.
The wallet code still uses a default fee for low-priority transactions of 0.1mBTC per kilobyte. During periods of heavy transaction volume, even this fee may not be enough to get transactions confirmed quickly; the mintxfee option may be used to override the default.

0.9.0 Release notes

RPC:
Command-line options:
Block-chain handling and storage:
Wallet:
Mining:
Protocol and network:
Validation:
Build system:
GUI:
submitted by allex2501 to BrasilBitcoin [link] [comments]

How to install Bitcoin Core Wallet and send Bitcoins r/bitcoin Using Walletconnect with Trust Wallet and the Binance Mainnet Dex Getting your Private Keys from the Bitcoin Core wallet ... Bitcoin.pl Poradnik #1 : Instalacja klienta Bitcoin-Qt

Coinbase is a secure platform that makes it easy to buy, sell, and store cryptocurrency like Bitcoin, Ethereum, and more. Based in the USA, Coinbase is available in over 30 countries worldwide. This is a set of changes updating wallet code to make fewer calls to Chain::Lock methods, so the Chain::Lock class will be easier to remove in #16426 with fewer code changes and small changes to behavior. Alright, let’s see how to unlock the wallet now. In most core wallets you’ll find the unlock wallet option under settings (Settings >> Unlock wallet). Just enter your passphrase to unlock your wallet. By unlocking from here you can access most part of your wallet. You can stake, send coins and even export private keys. (note that Bitcoin-Qt/bitcoind automatically re-transmit wallet transactions periodically until they are accepted into a block). Validate a transaction without broadcasting it . If you have a raw transaction and want to make sure all of its signatures are correct, you can use the signrawtransaction API call. Download the Bitcoin Wallet by Bitcoin.com. A simple, secure way to send and receive Bitcoin. Available for iOS, Android, Mac, Windows, and Linux. Supports Bitcoin Cash (BCH) and Bitcoin (BTC).

[index] [8575] [12609] [16687] [13086] [27394] [14904] [15720] [8914] [21171] [20852]

How to install Bitcoin Core Wallet and send Bitcoins

Bitcoin.pl Poradnik #1 : Instalacja klienta Bitcoin-Qt ----- Nasz poradnik w prosty i zrozumiały sposób przedstawi Ci wszystkie kroki potrzebne do zainstalowania klienta transakcji Bitcoin-Qt ... This video is unavailable. Watch Queue Queue. Watch Queue Let's update our Raven Core Desktop (QT) wallet to version 2.1! NOTE: Video is a little dated, but the basic steps still apply. Don't forget to SUBSCRIBE! ... DogeCoin QT Core Wallet Install plus Tips for Upcoming DogeThereum Fork - Duration: ... Install, Backup And Restore A Bitcoin Wallet. Or, Almost Any CryptoCoin Wallet (Windows) - Duration: 7:21. Syncing your Bitconnect QT wallet NEW updated 10/27/2018 - Duration: ... Is It Safe to Install a Desktop Bitcoin Wallet? - ... Off Chain with Jimmy Song 19,215 views.

#