How to store your bitcoins? – Orionkey-Crypto

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]

(Updated) [Staking] Reddcoin Core client GUI wallet on a Raspberry Pi Model 3B

Intro

This thread is an update to my first Reddcoin staking tutorial that was written 7 months ago.
 
The reason for the update
My Reddcoin Core software crashed and became unusable. My Raspberry Pi 3B would lag and freeze, I couldn't stake anymore.
 
Instead of just redoing everything the same way, I wanted to see if I could improve on 3 points:
 
The updates
 
If you would like to tip me
Writing a tutorial like this takes time and effort; tips are appreciated. My Reddcoin address: RqvdnNX5MTam855Y2Vudv7yVgtXdcYaQAW.
     

Overview

 

Steps

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
     

Video

https://www.youtube.com/watch?v=Snr5e8bzftI
This video shows how long it takes to start Reddcoin Core.   TL;DR:
     

Extra

Backup
Backup your wallet to prevent losing the RDDs in your wallet! There are two methods to backup, do both. Make new backups if you create a new receiving address!
 
 
   
Boot with only 1 USB drive plugged in:
Make sure only the USB drive (with the swap partition and data partition) is plugged in when you boot up your Raspberry Pi. This to make sure the swap partition (/dev/sda1) is recognized correctly.   If you boot up with multiple USB drives, Lubuntu might see the USB drive with the swap partition as the second drive (instead of the first drive), and ignore the 2 GB swap partition. If this happens, starting Reddcoin can render the Raspberry Pi unresponsive.
   
Connection issues If you have issues syncing the blockchain because you have 0 network connections, please follow the instructions in this thread.
   
Start Reddcoin Core easier
Run a shell script (.sh file), so you can start Reddcoin just by double clicking on an icon on your Desktop.
   
Minimization options
Adjust minimization options, so you can safely press on the X button (the close/exit button on the upper right corner).
   
RealVNC VNC Viewer (client) and VNC Connect (server): To remote connect to the Raspberry Pi, I use VNC Viewer ad VNC Connect from RealVNC.
 
   
Chromium as browser: The updates break Firefox, the browser crashes when you try to run it. Install another browser, Chromium, to solve this issue.
   
Updates / Upgrades
If Software Updater shows up and tells you that there is updated software available, do not install the updates using Software Updater. Use LXTerminal to update Lubuntu.  
     

Credits:

   
Credits in previous tutorial:
submitted by Yavuz_Selim to reddCoin [link] [comments]

EOT - Encryption of things

 **EOT - Encryption of things** 
There is a huge surge in devices attached to the internet, known as the Internet of Things, and it is estimated that over 80 Billion devices will be connected to the internet by 2025, from industrial machines to devices in our home. The constant hacking and cyber attacks have increased not only the demand but the necessity of secure solutions. Our privacy and digital footprint are at risk.
[b]Some examples where encryption plays a role:
[b]Secure messaging - To make messages truly secure we need a process whereby a cryptography can be applied to encrypt transaction.
[b]Secure calling - Secure calling is a process whereby the caller and the recipient of the call are identified and linked via a blockchain enabled cryptocurrency transfer, again creating public and private encryption keys making the call truly private.
[b]Secure media storage - To safely and securely store media a process is required where 1.) Access to the media is encrypted via public and private keys of the person wanting to store the media. 2.) The media itself needs to be encrypted with a set of encryption keys and 3.) Media storage costs need to be paid via cryptocurrency
[b]Secure browsing - To browse the internet securely we need to create a process of verification whereby nodes on the blockchain can verify websites as “safe”. Furthermore, the entire process needs to be encrypted as well.
[b]Verification - This is one of the most important uses of a blockchain, we can verify websites as in the example above but also various other things such as identity, title and ownership, date stamps and source of products as with the verification of the source of agricultural or other products. These are just a few examples. All of this data needs to be encrypted as well.
[b]“Smart home” security - Wi-Fi is often used for remote monitoring and control. Home devices, when remotely monitored and controlled via the Internet, are an important constituent of the Internet of Things - all needing encryption, otherwise, hackers paradise.
[b]EOT in the future - The examples we mentioned above are only “scratching the surface” of where these technologies are applicable and who knows what will be invented in future. Google, Apple and Uber are all testing cars that drive themselves. A major issue with this technology is again the security aspect and the need to protect against hacking and who want’s to get into a spaceship to Mars that might be hacked or hijacked by ransomware?
So the future for the [b]“Encryption of Things” – EOT, looks very interesting indeed and the role of crypto currencies in this will be major.
Read the full white paper here - http://eottoken.com/index.php/whitepape
The first device using EOT Coin is the BitVault®[/b] - the World's first crypto communicator and blockchain phone. The BitVault is a revolutionary new product that is built around security and privacy enabled through Blockchain technology. Biometric Security enabled through fingerprint and iris scan. Iris patterns are unique to you and are virtually impossible to replicate. This means that iris authentication is one of the safest ways to keep your BitVault locked and the contents private. Proven Biometric technology brings a whole new level of security to your crypto currency and blockchain transactions. Creating Military grade security for your device through third party independent Multilayer security.
September 2017 – Swiss Bank in Your Pocket integrates EOT Wallet(Achived)
October 2017 – BitVault®, the world’s first blockchain phone launches in London with integration of EOT for secure calling, secure messaging and secure browsing (First batch shipped)
November 2017 – BitVault® Global App Store launches for developers to develop their own applications (Achived)
November 2017 – Website EOT Payment Gateway for WordPress and WooCommerce (ACHIVED)
December 2017 – Cryptodoc stores all your documents securely and encrypted on your PC
December 2017 – Password Wallet stores all your passwords for applications and websites encrypted on your PC January 2018 – Smart Router for secure, encrypted internet which is direct, safe and easy
January 2018 – EOT Camera, an Encryption of Things connected camera
February 2018 – EOT Development Kit for hardware devices
EOT payment gateway live on swissbankinyourpocket.com, Now you can buy SBIYP and BitVault using EOT coins
More on the BitVault here:- https://swissbankinyourpocket.com/bitvault/]https://swissbankinyourpocket.com/bitvault/ https://swissbankinyourpocket.com/bitvault-apps/]https://swissbankinyourpocket.com/bitvault-apps/ https://bitcointalk.org/index.php?topic=2152534.0]https://bitcointalk.org/index.php?topic=2152534.0
JOIN US ON REDDIT : http://www.reddit.com/EncryptionOfThings]www.reddit.com/EncryptionOfThings JOIN US ON SLACK : [url=https://join.slack.com/t/eot-coin/shared_invite/enQtMjc3NzkxNzY5NzQ0LTFjMWI5NTJjOGEzYjU5ZDk0ZjRjZWE3MzBkNmI0MmQ2NTUzMTBkOGQ1YmEyNTllMmNiYzA3MGZjOGVmY2IyZGU
The EOT Token is trading on the Waves Platform, TOKENS are 1:1 image of EOT coins, EOT coins can be converted to tokens and vice versa using gateway service in SBIYP hardware wallet. if you do not have that hardware wallet, you can contact members on slack who have purchased SBIYP to do that swap for you.
TOKEN DETAILS
Name : EOT Token (Verified)
Identifier : GdnNbe6E3txF63gv3rxhpfxytTJtG7ZYyHAvWWrrEbK5
Total supply : 100,000,000
EOT token (EOT) markets added on the Tidex Exchange https://tidex.com/exchange/eot/btc https://tidex.com/exchange/eot/waves
EOT Coin details (currently minable)
https://github.com/EmbeddedDownloads/EOTCoin
windows wallet[/b] https://github.com/EmbeddedDownloads/EOTCoin/releases/download/v1.0.0.1/EOTCoin-win.exe
windows Desktop wallet[/b] https://github.com/EmbeddedDownloads/EOT-Coin-Windows-Desktop-Wallet/releases/download/1.0/EOTCoinDesktopWallet1-0.zip
MAC Wallet [/b] https://github.com/EmbeddedDownloads/EOTCoin/releases/download/v1.0.0.1/EOTCOIN-Qt-OSX-v1001.dmg
WEB wallet [/b] http://eot.digital (Closing, please withdraw your coins)
ANDROID wallet [/b] https://github.com/EmbeddedDownloads/EOTAndroidWallet/releases
Block Explorer [/b] http://www.eot.digital:3622/
Block Explorer 2 [/b] http://www.eotcoin.info (created by [b]@Luanptit[/b])
[Block reward [/b] 100 Coins, [b] ALGORITHM [/b] SCRYPT, [b] BLOCK TIME [/b] 90 seconds
MINING POOLS
Official mining pool [/b] http://www.eot.digital:3001/ Getting Started [/b] minerd -a scrypt -o stratum+tcp://www.eot.digital:3256 -u WalletAddressWhereYouWantYourMiningCoins -p 1
unofficial Mining pools http://www.altminer.net
http://antminepool.com
http://coinminers.net/
http://www.vivocryptopool.com
[red]Currently EOT is traded on WAVES DEX, Crypto-Bridge DEX and TIDEX. Big exchanges will be available soon, exchanges are in comkmunication.
Opportunities are available with EOT - from Development, Mining, Trading as well as other business opportunities built around the EOT currency and the "Encryption of Things"
[size=34px]Bitvault on Yahoo Finance https://finance.yahoo.com/news/bitvault-worlds-first-blockchain-phone-201600279.html [/size] [center][img width=770]https://i.imgur.com/UMIlRoC.png[/img][/center]
[center][size=30px]Press release 4th October 2017 [/size] [size=30px]yahoo Finance https://finance.yahoo.com/news/bitvault-announces-london-launch-161000826.html?soc_src=community&soc_trk=tw [img]https://i.imgur.com/mBDZnN7.png[/img]
Some Helpful Information
[quote author=Story777 link=topic=2091616.msg21890405#msg21890405 date=1505551168]
You have been keeping a great secret.
I've been doing a bit of research with the technology behind this coin. It looks like ALOT of research has gone into this tech, since about 2004 and shortly after a patent for this P2P system was quickly issued.
Bitvault (https://swissbankinyourpocket.com/product/bitvault/) who are using the worlds first blockchain phone as a secure communication device and ultimately taking [font=Verdana][b]encryption[/b][/font] to the Internet Of Things (IoT) keeping our personal and business data secure. All this is done using [b]EOT coin [/b](Encryption of Things).
In todays world insecure devices are rampant. Here are a couple of links about the CIA being able to use insecure devices to 'cause accidents' http://www.sandiegouniontribune.com/news/cyber-life/sd-me-wikileaks-cia-20170307-story.html and https://www.washingtonpost.com/news/innovations/wp/2017/03/08/what-we-know-about-car-hacking-the-cia-and-those-wikileaks-claims/
It's scary to think a legal entity could posses such power over life. Just the mere fact alone the governing authority can request phone records (e.g. txt msgs, voice msgs or eavesdropping) proves most if not all telecommunication companies do not encrypt, otherwise whats the point on requesting the information!? (legal or not).
Commercially sensitive information needs to be protected and most importantly in my opinion our [font=Verdana][b]rights[/b][/font] and the privacy of all citizens of the human race need to be protected.
From my understanding BitVault is a platform for reference data. This would be data that is stored for compliance reasons such as e-mails, invoicing systems and check imaging (e.g. high quality imaging for x-rays, MRI scans etc) and a prototype was developed in 2004. This would means massive amount of data storage is required with fail-safe systems so a authorised user could access this information very very quickly.
Three goals were needed to be achieved: Low cost, high reliability/availability and simplicity. This is the birth of Bitvault via EOT.
Bitvault ultimately stores immutable objects with each new version being updated and identified with a 160-bit key.
System stability is very important and must be immune to failure sequences. Parallel repair via indexing is one of the many strengths Bitvault has been able to demonstrate.
BitVault is a back-end system that uses [u][b]Applications[/b][/u] to catalog object ID's. Using a catalog utility and indexing within an application prevented scalability bottlenecking under heavy loads.
Fast forward 3 years to 2007 a very important decision was to [u][b]decentralise[/b][/u] BitVaults system. This in my opinion is one of the fundamental principles of cryptocurrency - [u][b]No one entity or person has any control of the data stored and only the authorised user can access this info[/b][/u]. Ultimate Security and thus personal safety (see above articles CIA hacks). BitVault using applications have been able to use provable communication and data storage with ease of retrieval with vital security measures.
BitVault is not alone in researching solutions for security for the IoT, such as Venti and the like are making progress, however, BitVault is 'head and shoulders' above the few competitors and are already offering practical working solutions on the market with huge scalability that is cost effective.
Well Done BitVault, well done EOT your secret is out and let the world embrace.
author=Story777 link=topic=2091616.msg21462424#msg21462424 date=1504428317]
I have had a response in Slack and it has satisfied my questions. Thank-you.
For everyone information here it is:
The currency was created with 200 Million EOT total supply on 7 July 2017 [ we showed it to the community a London Fintech week with the demonstration of the BitVault - fintechweek.com ]
100 Million was pre-mined and another 100 Million are currently being mined, 1 block every 90 seconds @ 100 coins per block.
So the pre-mined coins were listed on waves as a token so that it can create a market for the coins while we are working to get listed on other exchanges.
The 100 Million coins listed were distributed in several ways. Firstly, this was not an ICO because our business is already funded via private capital. We wanted to get the currency distributed a widely as possible. So most of the initial coins were given away to a number of interested parties. We distributed this to our whole development team, business partners, employees as well as to the waves and other communities. So we did not sell all these coins for the current price, most of it was given away for free to people that have an interest in our products and business. The price now is formed by whoever owns these coins.
The tokens on the exchange is really a representation of the currency and as such has value because it can be interchanged, just like Bitcoin and Ethereum are on the waves exchange. This whole process is explained on page 4 of the waves whitepaper, I think they call it an asset-to-asset exchange which makes it possible to list any asset that exist on waves. Unfortunately waves only has gateways currently for Bitcoin, Ethereum, Waves, Euro and USD, so we have to develop our own gateway, which will be available on Nov 1.
So to clarify 100,000,000 tokens costing $190M were not sold. It is a combination of airdrops, private sales and sales on the exchange.
Some EOT coins are needed because: "A lot of EOT will be distributed through our devices. For example our encrypted routers are pre-loaded with EOT, so we need that stock and it will be distributed that way".
And with the response to tokens on the Waves Exchange "This is how Bitcoin works on waves: - They created 21 Million BTC Tokens.. When you deposit Bitcoin into waves account, you receive an equal amount of tokens which you can either trade or even sent via the waves blockchain to another user.. Once you withdraw your tokens are exchanged for BTC and you receive it back into your BTC wallet.. Exactly the same for USD or EUR - You don't send Euro's to another client on waves if you transfer - you send a token that represents EUR -- This works exactly the w0083".
These are the answers I was looking for and make a lot of sense now. This is indeed an exciting project. :)
It's time to trade....
Now I have one question left....
Is there anyone using NiceHash to mine this coin?? I keep being disconnected because of the difficulty being too low. Can any one help?
[quote author=Shews link=topic=2091616.msg22876983#msg22876983 date=1507755312] EOT (coin) is now tradable on the CryptoBridge Decentralised Exchange, you can sign up below.
Please note this is for the EOT COIN ONLY, do not send tokens to this dex. This is a secure means to trade with the backend being on a blockchain. It is still in beta stage but has been working flawlessly so far. If you'd like more info I will post their website link is below.
https://wallet.crypto-bridge.org/?r=388691
You can sign up with a local wallet mode, meaning you are the only one with access to your keys, this is most secure. There is also the option to sign up with and account if you require access to you funds on the go.
More info:
https://crypto-bridge.org/
submitted by johningreece to crypto_currency [link] [comments]

Transcript from Ravencoin Open Developer Meeting - Nov. 16, 2018

Tron at 2:03 PM

Topics: Messaging (next phase) UI 2.2 - Build from develop - still working out a few kinks Mobile - Send/Rcv/View Assets - In progress Raven Dev Kit -Status

RavencoinDev at 2:04 PM

Hey Everybody! Let's get started!Thanks Tron for posting the topics.Tron is going talk about Messaging Plans.Let's start there.

Chatturga at 2:06 PM

It looks like this channel is not connected to the IRC. One moment

RavencoinDev at 2:07 PM

Well, we going to move forward as the tech guys fix the IRC connections.

Tron at 2:07 PM

I wanted to have a doc describing the messaging, but it isn't quite ready.I understand this isn't going to IRC yet, but I'm starting anyway.

RavencoinDev at 2:08 PM

Look for it soon on a Medium near you.

Tron at 2:08 PM

Summary version: Every transaction can have an IPFS hash attached.

Vincent at 2:09 PM

any plans for a 'create IPFS' button?

RavencoinDev at 2:09 PM

Yes

Vincent at 2:09 PM

on asset creatin window also?

RavencoinDev at 2:09 PM

Yes

Vincent at 2:09 PM

sweet

Tron at 2:09 PM

IPFS attachments for transactions that send ownership token or channel token back to the same address will be considered broadcast messages for that token.The client will show the message.Some anti-spam measures will be introduced.If a token is in a new address, then messages will be on by default.The second token in an address, the channel will be available, but muted by default.

RavencoinDev at 2:11 PM

That way I can't spam out 21b tokens and then start sending messages to everybody.

Tron at 2:11 PM

We'd like to have messaging in a reference client on all six platforms.

corby at 2:11 PM

Hi!

Tron at 2:11 PM

Photos will not be shown. Messages will be "linkified"

RavencoinDev at 2:12 PM

and plain text.We'll start with the QT wallet support

Tron at 2:12 PM

Any other client is free to show any IPFS message they choose.The messaging is fully transparent.

Rikki RATTOE at 2:13 PM

ok, so messaging isn't private

Tron at 2:13 PM

Anyone could read the chain and see the messages.

RavencoinDev at 2:13 PM

No, never was planned to be private

MSFTserver-mine more @ MinerMore at 2:13 PM

irc link should be fixed

Tron at 2:13 PM

It is possible to put encrypted content in the IPFS, but then you'd have to distribute the key somehow.

RavencoinDev at 2:13 PM

Thanks MSFT!

Chatturga at 2:13 PM

Negative

Tron at 2:14 PM

Core protocol changes Extend the OP_RVN_ASSET to include for any transfer: RVNT <0xHH><0x12><0x20><32 bytes encoding 256 bit IPFS hash> 0xHH - File type 0x00 - NO data, 0x01 - IPFS hash, 0x02 through 0xFF RESERVED 0x12 - IPFS Spec - Using SHA256 hash 0x20 - IPFS Spec - 0x20 in hex specifying a 32 byte hash. …. (32 byte hash in binary)

corby at 2:14 PM

By it's nature nothing on chain is private per se. Just like with wallets you'd need to use crypto to secure messaging between parties.

Tron at 2:14 PM

Advantages: This messaging protocol has the advantage of not filling up the blockchain. The message information is public so IPFS works as a great distributed store. If the messages are important enough, then the message sender can run nodes that "PIN" the message to keep a more durable version. The message system cannot be spoofed because any change in the message will result in a different hash, and therefore the message location will be different. Only the unique token holder can sign the transaction that adds the message. This prevents spam. Message clients (wallets), can opt-in or opt-out of messages by channel. Meta-message websites can allow viewing of all messages, or all messages for a token. A simple single channel system is supported by the protocol, but a channel could be sub-divided by a client to have as many sub-channels as desired. There are no limits on the number of channels per token, but each channel requires the 5 RVN fee to create the channel.

RavencoinDev at 2:14 PM

So, somebody could create their own client and encrypt the data on the blockchain if they wished.

corby at 2:15 PM

Wow Tron types fast

Rikki RATTOE at 2:15 PM

yeah there was some confusion in the community whether messaging would be private and off chain

Tron at 2:15 PM

Anti-Spam Strategy One difficulty we have is that tokens can be sent to any Ravencoin asset holder unsolicited. This happens on other asset platforms like Counterparty. In many cases, this is good, and is a way for asset issuers to get their token known. It is essentially an airdrop. However, combined with the messaging capabilities of Ravencoin, this can, and likely will become a spam strategy. Someone who wants to send messages (probably scams) to Ravencoin asset holders, which they know are crypto-savvy people, will create a token with billions of units, send it to every address, and then message with the talking stick for that token. Unless we preemptively address this problem, Ravencoin messaging will become a useless spam channel. Anyone can stop the messages for an asset by burning the asset, or by turning off the channel. A simple solution is to automatically mute the channel (by default) for the 2nd asset sent to an address. The reason this works is because the assets that you acquire through your actions will be to a newly generated address. The normal workflow would be to purchase an asset on an exchange, or through a ICO/STO sale. For an exchange, you'll provide a withdrawal address, and best practice says you request a new address from the client with File->'Receiving addresses…'->New. To provide an address to the ICO/STO issuer, you would do the same. It is only the case where someone is sending assets unsolicited to you where an address would be re-used for asset tokens. This is not 100% the case, and there may be rare edge-cases, but would allow us to set the channels to listen or silent by default. Assets sent to addresses that were already 'on-chain' can be quarantined. The user can burn them or take them out of quarantine.

RavencoinDev at 2:18 PM

Okay, let me know when/if you guys read through all that. 📷📷2

corby at 2:18 PM

To be clear this is a client-side issue -- anyone will be able to send anything (including messages) to any address on chain..

RavencoinDev at 2:18 PM

It'll be in the Medium post later.

Tron at 2:19 PM

@corby The reference client will only show messages signed by the issuer or designated channels.Who is ready for another wall of text? 📷

corby at 2:19 PM

I hear that's the plan 📷 just pointing out that it is on the client in these cases..

Tron at 2:20 PM

Yes, any client can show anything gleaned from the chain.Goal: A simple message format without photos. URL links are allowed and most clients will automatically "linkify" the message for valid URLs. For display, message file must be a valid json file. { "subject":"This is the optional subject", "message": "This is required.", "expires": 1578034800 } Only "message" is required {"message":"Hello world"}

bhorn at 2:21 PM

expires?

Vincent at 2:21 PM

discount coupon?

Tron at 2:21 PM

If you have a message that worthless (say after a vote), just don't show the message.

bhorn at 2:21 PM

i see - more client side operation

corby at 2:21 PM

/expires

Tron at 2:22 PM

Yep. And the expiration could be used by IPFS pinners to stop worrying about the message. Optional

RavencoinDev at 2:22 PM

If the client sees a message that is expired it just won't display it.

Vincent at 2:23 PM

will that me messaged otherwise may cause confusion?"expired'

RavencoinDev at 2:23 PM

YesWe'll do our best to make it intuitive.

Tron at 2:24 PM

Client handling of messages Pop-up messages or notifications when running live. Show messages for any assets sent to a new address - by default Mute messages for assets sent to an address that was already on-network. Have a setting to not show messages older than X IPFSHash (or 8 bytes of it) =

Rikki RATTOE at 2:25 PM

will there be a file size limit for IPFS creation in the wallet?

RavencoinDev at 2:25 PM

We'll also provide updated documentation.

Tron at 2:26 PM

Excellent question Rikki. Here are some guidelinesGuidelines: Clients are free to show or not show poorly formed messages. Reference clients will limit message display to properly formed messages. If subject is missing, the first line of the message will be used (up to 80 chars). Standard JSON encoding for newlines, tabs, etc. https://www.freeformatter.com/json-escape.html Expiration is optional, but desired. Will stop showing the message after X date, where X is specified as Unix Epoch. Good for invites, voting requests, and other time sensitive messages that have no value after a specific date. By default clients will not show a message after X blocks (default 1 year) Amount of subject shown will be client dependent - Reference client may cut off at 80 chars. Messages longer than 15,000 (about 8 pages) will not be pinned to IPFS by some scanners. Messages longer than 15,000 characters may be rejected altogether by the client. Images will not be shown in reference clients. Other clients may show any IPFS content at their discretion. IPFSHash is only a "published" message if the Admin/Owner or Channel token is sent from/to the same address. This allows for standard transfers with metadata that don't "publish".Free Online JSON Escape / Unescape Tool - FreeFormatter.comA free online tool to escape or unescape JSON strings

RavencoinDev at 2:26 PM

We're hoping to add preferences that will allow the user to customize their messaging experience.

Tron at 2:27 PM

Also, happy to receive feedback from everyone.

corby at 2:27 PM

In theory though if you maintain your own IPFS nodes you should be able to reference files of whatever size right?

Steelers at 2:27 PM

How about a simple Stop light approach - Green (ball) New Message, Yellow (Ball) Expiring Messages, Red (Ball) Expired Messages

RavencoinDev at 2:27 PM

Yes please! That's the point of sharing it here

Chatturga at 2:27 PM

Fixt

push | ravenland.org at 2:28 PM

Thanks @Tron can you provide any details of the coming 'tooling' at the end of november, and what that might enable (apologies as I am a bit late to meeting if this has been asked already)

VeronicaBOT at 2:28 PM

sup guys

Tron at 2:28 PM

Sure, that's coming.

RavencoinDev at 2:28 PM

That's the Raven WebDev Kit topic coming up in a few mins.

push | ravenland.org at 2:29 PM

oki 📷 cheers

RavencoinDev at 2:29 PM

Questions on messaging?

Jeroz at 2:30 PM

Not sure if I missed it, but how fast could you send multiple messages in succession?

BruceFenton at 2:30 PM

Some kind of sweep feature or block feature for both tokens and messages could be useful Certain messages will be illegal to possess in certain jurisdictions If someone sends a picture of Tiennneman tank man in China or a message calling for the overthrow of a ruler it could be illegal for someone to have There’s no way for that jurisdiction to censor the chain So some users might want the option to purge messages or not receive them client side / on the wallet

Tron at 2:30 PM

Messages are a transaction.

RavencoinDev at 2:30 PM

So it'll cost you to spam messages.They can only send a hash to that picture and the client won't display anything not JSON

corby at 2:31 PM

purge/block is the age old email spam

Tron at 2:31 PM

The Reference client - other clients / web sites, etc can show anything they wish.

RavencoinDev at 2:31 PM

You can also burn a token if you never want to receive messages from that token owner.

UserJonPizza|MinePool.com|Mom at 2:32 PM

Can't they just resend the token?

Tron at 2:33 PM

Yes, but it would default to mute.📷2

RavencoinDev at 2:33 PM

meaning it would show up in a spam foldetab

bhorn at 2:33 PM

is muting available for the initial asset as well?

RavencoinDev at 2:33 PM

Something easy to ignore if muted.

Tron at 2:33 PM

@bhorn Yes

BruceFenton at 2:33 PM

Can users nite some assets and not others?

Tron at 2:33 PM

@bhorn It just isn't the default.

BruceFenton at 2:33 PM

Mute

RavencoinDev at 2:33 PM

YesYou can mute per token.

BruceFenton at 2:34 PM

Great

Tron at 2:34 PM

And per token per channel.

Jeroz at 2:34 PM

channels are the subtokens?

BruceFenton at 2:34 PM

What’s per token per channel mean ?

Tron at 2:34 PM

The issuer sends to the "Primary" channel.Token owner can create channels like "Alert", "Emergency", etc.These "talking sticks" are similar to unique assets.📷1ASSET~Channel

RavencoinDev at 2:37 PM

Okay, we have a few more topics to cover today.Tron will post more details on Medium and we can continue discussions there.

Jeroz at 2:38 PM

Ah, I missed channel creation bit for each token with the 5 RVN / channel cost. It makes more sense to me now.

RavencoinDev at 2:38 PM

The developers are working towards posting a new version 2.2 that has the updated UI shown on twitter.

Vincent at 2:39 PM

twit link?

RavencoinDev at 2:39 PM

The consuming of large birds (not ravens) might slow the release a bit.So likely the week after Thanksgiving.

[Dev] Blondfrogs at 2:39 PM

The new UI will contain: - New menu layout - New icons - Dark mode - Added RVN colors

Dan1666 at 2:39 PM

+1 Dark mode

RavencoinDev at 2:39 PM

DARK MODE!

Dan1666 at 2:40 PM

so pleased about that

RavencoinDev at 2:40 PM

I can honestly say it'll be the nicest crypto wallet out there.

[Dev] Blondfrogs at 2:40 PM

A little sneak peak, but this is not the final project📷📷6📷3

!S1LVA | MINEPOOL at 2:40 PM

Outstanding

Dan1666 at 2:41 PM

reminds me of Sub7 ui for those that might remember

UserJonPizza|MinePool.com|Mom at 2:41 PM

Can we have an asset count at the top?

[Dev] Blondfrogs at 2:41 PM

Icons will be changing

Vincent at 2:41 PM

does the 'transfer assets' have a this for that component?

Tron at 2:41 PM

Build from develop to see the sneak preview in action.There may be small glitches depending on OS. These are being worked on.

Rikki RATTOE at 2:41 PM

No plans for the mobile wallet to show an IPFS image I'm assuming? Would be a nice feature if say a retail store could send a QR coupon code to their token holders and they could scan the coupon using their wallet in store

[Dev] Blondfrogs at 2:42 PM

@Vincent That will probably be a different section added later📷1

RavencoinDev at 2:42 PM

Yes, Rikki we do want to support messaging.Looking into how that would work with Apple and Google push.

push | ravenland.org at 2:42 PM

sub7📷1hahaoldschoolit so is similar aswell

[Master] Roshii at 2:43 PM

Messages are transactions no need for any push

Tron at 2:43 PM

@Rikki RATTOE There's a danger in showing graphics where anyone can post anything without accountability for their actions. A client that only shows tokens for a specific asset could do this📷1

RavencoinDev at 2:43 PM

True, unless you want to see the messages even if you haven't opened your wallet in a week.

Rikki RATTOE at 2:44 PM

the only thing I was thinking was if you simply linked the image, somebody could just copy the link and text it off to everyone and the coupon isn't all that exclusive

UserJonPizza|MinePool.com|Mom at 2:44 PM

Maybe a mobile link-up for a easy way to see messages by just importing pubkey(edited)

RavencoinDev at 2:45 PM

Speaking of mobileWe are also getting close to a release of mobile that includes the ability to show assets held, and transfer them.Roshii has been hard at work.📷6📷1

Vincent at 2:46 PM

can be hidden also?

RavencoinDev at 2:47 PM

We're still finalizing the UI design but that is on the list of todos📷1

Under at 2:47 PM

Could we do zerofee mempool messaging that basically gets destroyed after it expires out of the mempool for real-time stealth mode messaging

corby at 2:48 PM

That's interesting!

RavencoinDev at 2:49 PM

There are other solutions available for stealth messaging, that's not what the devs had intended to build. It does sound cool though @Under

Under at 2:50 PM

📷 we’ll keep up the good work. Looking forward to the db upgrades. Will test this weekend

RavencoinDev at 2:50 PM

Thanks!That leaves us with 10 minutes for the Dev Kit!Corby has been working on expanding some of the awesome work that @Under has been doing.

corby at 2:52 PM

Yes -- all of the -addressindex rpc calls are being updated to work with assets

RavencoinDev at 2:52 PM

Hopefully we'll be able to post the source soon once the initial use cases are all working.

corby at 2:52 PM

so assets are being tied into transaction history, utxos, etc

RavencoinDev at 2:52 PM

The devs want to provide a set of API's that make it easy for web developers to build solutions on top of Ravencoin.VinX is investigating the possibility of using Ravencoin to power their solution.

corby at 2:53 PM

will be exposed via insight-api which we've forked from @Under

[Master] Roshii at 2:53 PM

Something worth bringing up is that you will be able to get specific asset daba from full nodes with specific message protocols.

corby at 2:54 PM

also working on js lib for client side construction of asset transactions

Tron at 2:55 PM

Dev Kit will be an ongoing project so others can contribute and extend the APIs and capabilities of the 2nd layer.📷3📷3

RavencoinDev at 2:55 PM

Will be posted soon to the RavenProject GitHub.

corby at 2:55 PM

separate thing but yes Roshii that is worth mentioning -- network layer for getting asset data

RavencoinDev at 2:55 PM

Again want to give thanks to @Under for getting a great start on the project

push | ravenland.org at 2:56 PM

Yes looking forward to seeing more on the extensive api and capabilities, is there a wiki on this anywhere tron?(as to prevent other people replicating eachothers work?)

RavencoinDev at 2:56 PM

The wiki will be in the project on GitHub

push | ravenland.org at 2:56 PM

im guessing when the kit is released, something will appear, okok cool

RavencoinDevat 2:57 PM

Any questions about the Web DevKit?

push | ravenland.orgToday at 2:57 PM

well, what kind of support will it give us, that would be nice, is this written anywhereI'm still relatively new to blockchain<2 yearsso need some hand holding i suppose 📷

bhorn at 2:58 PM

right, what are initial use cases of the devkit?

push | ravenland.org at 2:58 PM

i mean im guessing metamask like capabilitysome kind of smart contract, some automation capabilitiesrpc scriptsstuff like thiseven if proof of concept or examplei guess im wondering if my hopes are realistic 📷

RavencoinDev at 2:59 PM

You can see the awesome work that @Under has already don that we are building on top of.

push | ravenland.org at 2:59 PM

yes @Under is truly a herooki, cool

RavencoinDev at 2:59 PM

https://ravencoin.network/Ravencoin Block ExplorerRavencoin Insight. View detailed information on all ravencoin transactions and blocks.

push | ravenland.org at 2:59 PM

ok, sweet, that is very encouragingthanks @Under for making that code public

corby at 3:00 PM

It will hopefully allow you to write all sorts of clients -- depending on complexity of use case you might just have js lib (wallet functions, ability to post txs to gateway) or a server side project (asset explorer or exchange)..(edited)

Tron at 3:00 PM

Yeah, thanks @Under .

RavencoinDev at 3:00 PM

What's your GitHub URL @Under ?

push | ravenland.org at 3:00 PM

https://github.com/underdarkskies/ i believeGitHub· GitHubunderdarkskies has 31 repositories available. Follow their code on GitHub.📷

RavencoinDev at 3:00 PM

Yup!

push | ravenland.org at 3:00 PM

he is truly a hero(edited)

RavencoinDev at 3:00 PM

LOL

push | ravenland.org at 3:00 PM

damn o'sgo missing everywhere

RavencoinDev at 3:01 PM

teh o's are hard... Just ask @Chatturga

push | ravenland.org at 3:01 PM

📷

Chatturga at 3:01 PM

O's arent the problem...

push | ravenland.org at 3:01 PM

📷📷

RavencoinDev at 3:02 PM

Alright we're at time and the devs are super busy. Thanks everybody for joining us.

push | ravenland.org at 3:02 PM

thanks guys

RavencoinDev at 3:02 PM

Thank you all for supporting the Raven community.📷6

corby at 3:02 PM

thanks all!

push | ravenland.org at 3:02 PM

keep up the awesome work, whilst bitcoin sv and bitcoin abc fight, another bitcoin fork raven, raven thru the night📷5

Vincent at 3:02 PM

piece!!

RavencoinDev at 3:03 PM

We're amazingly blessed to have you on this ride with us.📷5📷9📷5

Dan1666 at 3:03 PM

gg

BruceFenton at 3:03 PM

📷📷12📷4

UserJonPizza|MinePool.com|Mom at 3:55 PM

Good meeting! Excited for the new QT!!
submitted by Chatturga to u/Chatturga [link] [comments]

Lore v2 QT on Raspberry Pi

Hello,
 
To follow up to mindphuk's excellent piece on building the headless client on Raspberry Pi (https://www.reddit.com/blackcoin/comments/6gkjrw/wip_blackpi_a_stake_device_based_on_raspberry/), I thought if anyone was interested I'd show you how to get the full QT version running on the Pi on the Jessie with Pixel desktop. This works and has been soak tested for several days now on a standard Raspberry Pi 3. I have since added some coins and it stakes a handful of times a day.
 
Running staking Lore clients paves the way for some of the future use cases of BLK utilising the Bitcoin 0.12 (and newer) core tech, including colored coins. So I'm going to leave this one going indefinitely to kickstart the number of Lore clients staking. It's certainly not mandatory but it will be good in the longer term to have a nice distribution of Lore staking clients.
 
The cross-compile which lets you create binaries for multiple platforms didn't work for the QT version on the Pi, so there is more to do than just running the binary unfortunately, as below. There are folks working on some much cleaner solutions than this for the Pi, with a custom front end, and where you won't have to do any mucking about. That is coming soon. In the meantime, if you enjoy a fiddle with such things, here's how to get this QT client working on your Pi.
 
These instructions assume you are starting from scratch with a completely blank OS.
 
Download Jessie with Pixel from: http://downloads.raspberrypi.org/raspbian/images/raspbian-2017-07-05/2017-07-05-raspbian-jessie.zip
 
Note they have since (August 2017) released a version called 'Stretch' which does not work with this guide. I'll see if I can come up with something new for that at some point and link to it here when I have. In the meantime the guide should work with the Jessie image above.
 
Unzip the file and extract the .img file to burn it onto Fresh SD card to boot from (to be safe, use 16GB or larger), using a tool like win32diskimager or Etcher.
 
Assuming you have keyboard/mouse and monitor plugged into your pi, boot it up and the Jessie Desktop will show.
 
Before we do anything else, you should increase the default swap size on the pi, as compiling certain libraries can exhaust the RAM and get stuck otherwise. To do this, launch a Terminal window and type:
 
sudo nano /etc/dphys-swapfile 
 
and Change the CONF_SWAPSIZE from 100 to:
 
CONF_SWAPSIZE=1024 
 
Exit nano with control + x to write out the file.
 
Then, run the following to restart the swapfile manager:
 
sudo /etc/init.d/dphys-swapfile stop sudo /etc/init.d/dphys-swapfile start 
 
Now, launch the browser and download the Lore 2.12 binaries for ARM here: https://mega.nz/#!k2InxZhb!iaLhUPreA7LZqZ-Az-0StRBUshSJ82XjldPsvhGBBH4 (Version with fee fix from 6 September 2017)
 
(If you prefer to compile it yourself instead, it is possible by following the instructions in the original article by Mindphuk just taking into account this is the newer version of the Lore client than when that was written (https://github.com/janko33bd/bitcoin/releases) and the versions of Boost and the Berkeley DB need to be the same as below.)
 
Double click the zip and extract the Lore binary files. Yes, at the moment they are all called 'bitcoin', not 'blackcoin' or 'Lore' - this is because the code derives from a recent bitcoin core implementation so this has not yet been updated. You can place these wherever you like.
 
In the Terminal window, change directory to where you put the binaries, e.g.:
 
cd Downloads/lore-raspberrypi-armv7-jessie-pixel chmod +x * 
 
That marks the binaries as executable.
 
Now, we need the Boost libraries installed for any of the Lore binaries to work. The project was done with Boost 1.62.0. Unfortunately the Jessie repository only goes up to 1.55, so we need to download and build 1.62 manually on the device.
wget https://sourceforge.net/projects/boost/files/boost/1.62.0/boost_1_62_0.tar.gz/download tar -xvzf download cd boost_1_62_0 sudo ./bootstrap.sh sudo ./b2 install 
 
(This will take almost 2 hours. Have a nice cup of tea and a sit down.)
 
When I came to run the binaries, I found they couldn't find Boost. Running this command fixes that:
sudo ldconfig 
 
Now we are going to install the packages which aren't already included in the default OS installation which the binaries need in order to run:
sudo apt-get install qrencode libprotobuf-dev libevent-pthreads-2.0-5 
 
Now we need to install the Berkeley Database version 6.2.23. This is the version Lore v2 uses. Bitcoin still uses 4.8 which is 10 years old! This doesn't take too long.
wget http://download.oracle.com/berkeley-db/db-6.2.23.tar.gz tar -xvzf db-6.2.23.tar.gz cd db-6.2.23/build_unix ../dist/configure --prefix=/usr --enable-compat185 --enable-dbm --disable-static --enable-cxx 
 
I find this next section of the Berkeley instructions worked better just switching to root, which can be fudged by running sudo su before the rest:
sudo su make make docdir=/usshare/doc/db-6.2.23 install chown -v -R root:root /usbin/db_* /usinclude/db{,_185,_cxx}.h /uslib/libdb*.{so,la} /usshare/doc/db-6.2.23 
 
Now we're going to go up a couple of directories to where the binaries were:
cd ../.. 
 
Then run the client!
./bitcoin-qt 
 
And there you have it. Should hopefully end up looking a bit like this: http://imgur.com/a/eEHGa
 
Using the Bootstrap can save a while syncing. Download it at: https://www.reddit.com/blackcoin/comments/6b3imq/blackcoin_bootstrapdat_up_to_block_1631800
 
Place the bootstrap.dat file into the ~/.lore directory.
 
Run ./bitcoin-qt again, it will say 'Importing Blocks' rather than 'Synchronising with Network'. My pi sync'ed fully in about 5-6 hours.
 
If you want peace of mind that Lore will always start on bootup into the Jessie w/Pixel desktop (i.e. after a power cycle), then you need to create a .desktop file in the following place.
sudo nano ~/.config/autostart/Lore.desktop 
 
And in it, enter the following (tailoring the Exec line below to the whereabouts of your bitcoin-qt file):
[Desktop Entry] Name=Blackcoin Lore Comment=Mining without the waste Exec=/home/pi/Downloads/lore-raspberrypi-armv7-jessie-pixel/bitcoin-qt Type=Application Encoding=UTF-8 Terminal=false Categories=None; 
 
Power usage and payback time
 
After a good while leaving it going by itself, the CPU load averages got down to almost zero, all of the time. Idling, the Pi uses a bit less than 3 watts. This means it would take two weeks to use one 1Kw/h of electricity.
 
If you pay e.g. 12.5 cents a unit, that's what you'd expect this to cost to run in a fortnight. That's around $0.25 a month or $3 a year. Green and cheap and helping to secure the BLK network. I paid for the year's worth of electricity in 2 days staking with 25k BLK. Makes mining look silly, huh? ;)
 
Securing your Pi
 
With staking, your wallet needs to be unlocked and as such, the keys to your wallet are on the device. In a clean and newly installed environment as described above, and if you don't allow others to use your device and there is no other software or nasties running on it, there is no real cause for concern. However, there are some basic security precautions you can take.
 
Firstly, if you have enabled SSH and are playing with your pi across your LAN (or worse, the Internet), you should immediately change the password for the default 'pi' user (which is preconfigured to be 'raspberry'). Simply log in as normal, then type:
 
passwd 
 
You'll be prompted to enter the old and the new passwords.
 
Security by default
 
Your Pi is likely, by default, to not be exposed to incoming connections from the outside world because your router is likely generating a private address range for your LAN (192.168.x.x or 10.0.x.x or 172.x.x.x) which means all incoming connections are effectively blocked at the router anyway unless you set up a 'port forward' record to allow packets arriving on certain ports to be forwarded to a specific internal IP address.
 
As for accessing your Pi across the internet, if you have set up a port forward, this likely has security ramifications. Even basic old fashioned protocols have proven in recent times to have uncaught flaws, so it's always advisable to lock down your device as much as possible, and even if you only plan to access the Pi over your LAN, install a firewall to configure this. I used one called ufw, because it's literally an uncomplicated firewall.
 
sudo apt-get install ufw sudo ufw allow from 192.168.0.0/16 to any port 22 sudo ufw --force enable 
 
This allows just port 22 (SSH) to be open on the Pi to any device on my LAN's subnet (192.168.0.x). You can change the above to a single IP address if paranoid, or add several lines, if you want to lock it down to your LAN and a specific external static IP address (e.g. a VPN service you use). To find out what subnet your router uses, just type:
 
ifconfig 
 
and you'll see on the interface you are using (either hard wired or wifi) the 192.168 or 10. or 172. prefix. Change the above rule so it matches the first two octets correctly (e.g. 10.0.0.0/16 if you're on a 10.0. address).
 
You may already use VNC to access your Pi's desktop across your LAN, this uses port 5900. Add a line like above to lock it down to an internal address. It's not a good idea to expose this port to the wider world because those connections are not encrypted and potentially could be subjected to a MITM attack.
 
You can query the status of the firewall like this:
ufw status 
 
And of course, try connecting remotely once you change the rules to see what works. You should consult the official documentation for further options: https://help.ubuntu.com/community/UFW
 
Back up & Recovery
 
There are again many ways to tackle this so I'll just speak about my basic precautions in this regard. Don't take it as a be-all-and-end-all!
 
The wallet.dat file is the key file (literally) containing all the private/public keys and transactions. This can be found in:
 
~/.lore 
 
You can navigate there using Jessie w/Pixel's own file manager or in a terminal window (cd ~/.lore). You can copy this file or, if you'd rather keep a plain text file of all your public and private keys, use the 'dumpwallet' command in the console. In Lore, go to Help > Debug Window > Console and type 'dumpwallet myfilename' where myfilename is the file you want it to spit out with all your keys in it. This file will end up in the same place you launch bitcoin-qt from.
 
The instructions earlier on, when running Lore for the first time intentionally left out encrypting your wallet.dat file because in order for the wallet to stake upon startup, it needs to have a decrypted key already. This isn't perfect, but after a power cycle, it would never stake unless you left it decrypted. So the best practice here is as soon as the wallet.dat file has left your device, i.e. you copy it to a USB stick for example, put it in an encrypted folder or drive (or both).
 
In Windows, one way is to use Bitlocker drive encryption for the entire drive. You should follow the instructions here to encrypt your flash drive before your wallet.dat is on there, and don't forget the password!!
http://infosec.nmsu.edu/instructions-guides/how-to-enable-bitlocker-to-go-for-external-hard-drives-and-usb-flash-drives/
 
On the Mac, I use a software package called Concealer to encrypt files I store on the Mac itself: http://www.belightsoft.com/products/conceale   There are almost certainly free packages with similar functionality, I have just used that one for years.
 
Either way, if you want to just make sure your USB drive is encrypted, you can do so in one-click in Finder before you put the sensitive files on it: http://lifehacker.com/encrypt-a-usb-stick-in-finder-with-a-click-1594798016
 
Note that these disk encryption methods may mean having to access the USB stick on a PC or Mac in order to retrieve the files in the event of a disaster. Be aware this may mean exposing them to more security issues if your computer is in any way compromised or someone nefarious has access to your computer. There are more 'manual' ways of backing up and recovering, such as literally writing down private/public key pairs which this guide doesn't go into, but may suit you better if paranoid about your setup.
 
Recovery
 
The wallet.dat file has everything in it you need to recover your wallet, or if you used 'dumpwallet', the file you saved out has all the keys.
 
Wallet.dat method: Install Lore as normal then replace any auto-generated wallet.dat in ~/.lore directory with your backup. If a lot of time has elapsed and many transactions have occurred since your backup, launch lore with:
./bitcoin-qt -rescan 
 
And if that doesn't do the job, do a full reindex of the blockchain:
 
./bitcoin-qt -reindex 
 
If you used the dumpwallet command, install Lore then place the file containing all the keys that you saved out in the same directory as bitcoin-qt. In Lore, go to Help > Debug Window > Console and type 'importwallet myfilename' where myfilename is that file containing all the keys. The wallet should automatically rescan for transactions at that point and you should be good to go.
 
There are a million ways to do effective security and disaster recovery, but I hope this shows you a couple of basic precautionary ways. There are discussions about better ways to stake without compromising too much security which are happening all the time and developments in this regard will happen in time.
 
In the meantime, feel free to comment with your best practices.
 
submitted by patcrypt to blackcoin [link] [comments]

CRAVE Roadmap Details Current and completed

Q1 - All Complete
Coinswap Ending: CRAVE held a coin swap to implement a new code base, blockchain, features, and wallet. The supply was also increased to better fit zCRAVE denominations. Any remaining coins were burned, staying true to the 'No Premine' aspect of CRAVE.
Cryptopia Listing: Application and payment fee for listing CRAVE on the exchange, Cryptopia.
Update Website: Addition of more languages, roadmap, and auto-updating statics to the official website.
Coinomi Integration: Secure, lightweight, universal HD wallet for Bitcoin and other cryptocurrencies
--------------------------------------------------------------------------------------------------------------------------------------------------------
Q2
Completed:
White Paper: Inform the public of the project, features, and goals of CRAVE.
CRAVE Redesign: A fresh new logo and website design to get CRAVE adopted to a wider audience.
Governance & Budget System Activation: Community members can propose ideas and projects, which masternode holders will then be able to vote for or against. This method allocates funds set aside from the CRAVE block rewards to fund projects that support the network.
Q2 Upcoming Updates:
Brainwallet Integration: Storage of the user's zCRAVE will be available with a mnemonic, one-seed recovery phrase.
Crave Knowledge Base: Crave’s own medium to answer common questions that users have, ranging from beginner to advanced levels.
Website Upgrades: Improvements will be made to add all important information in a single user-friendly location. Paper Wallet Generator: Support for an offline mechanism of storing public & private keys on paper
---------------------------------------------------------------------------------------------------------------------------------------------------------
Q3
zCRAVE Staking: The network mixing security will be Increased by allowing the staking of zCRAVE
New Wallet Design: Complete reworking of the wallet UI for increased usability
In-Wallet Voting: Support for performing budget voting from the QT wallet’s GUI
In-Wallet Proposals: Support for performing all governance functions from the QT wallet’s GUI
----------------------------------------------------------------------------------------------------------------------------------------------------------
Q4
Adaptive Blocks: Block sizes will automatically adjust to current network requirements, allowing for faster transactions and increased scalability
I2P Network Integration: Invisible Internet Project (I2P) is an anonymous network layer that allows for censorship-resistant peer to peer communication. When implemented with CRAVE, this will also serve to encrypt network traffic so that the user's IP address cannot be accessed.
submitted by alex61688 to craveproject [link] [comments]

How To Use Coin Control & Stake More With 'PoS' DEAL Coins

How To Use Coin Control & Stake More With 'PoS' DEAL Coins
When you are using Proof of Stake (PoS) coins, active coin control is essential to ensuring that you maximize your PoS rewards. If you do not use coin control you may benefit less from the compounding of your rewards, and you may lose more rewards than necessary when you make a payment from your wallet.
Exactly how much difference this makes will depend on the specifications of the coin itself, and what transactions you make. It is particularly important for coins such as IdealCash, in which small and medium-sized holders must wait a long time between each time they stake and get a reward.
This presents a manual method of coin control for users of Qt wallets!
Why You Need to Use Coin Control
As I already stated, small and medium-sized IdealCash holders must wait a long time before they stake. When you do finally get to stake some coins, you do not get the interest due on your whole balance; instead, one of the payments you have received is selected and you earn the rewards due on that amount. The rest of your interest is not lost, it keeps building up and you get it later. But what this means is that if you receive a single payment for 10,000 coins, for example, you will earn more compound interest than if you receive 10 payments for 1,000 coins, even though your balance is the same. This is because in both cases you will wait the same amount of time before getting your first reward, but in the first instance you will receive all of your interest at once, whereas in the second example you will receive only 10% as much on your first stake. Because you can earn PoS rewards on your PoS rewards (compounding) that mean you will eventually end up with more money in the first example when you got a single payment than you would in the second example where you got 10 payments that added up to the same amount.
In the example above you could easily fix this without getting into any advanced techniques simply by using your wallet in the ordinary way to send yourself 10,000 coins. By doing this you would combine all of the outputs – all 10 of the 1,000 IdealCash payments – into a single output. But sometimes things can be a little more complicated. For example, let's say you receive a single payment of 10,000 coins, and leave it in your wallet to stake. After 8 weeks you still haven’t earned your first reward, but have built up a nice bit of ‘interest owed’ on these coins. You now receive those 10 payments for 1,000 each we looked at before. When you spend any coins in your wallet, you lose the unpaid rewards owed to you for staking them. So in this example, you would want to send a 10,000 IdealCash payment to yourself using these 10 new payments. But if you simply use the wallet as normal to send a payment to yourself it will probably not do this – it will use the 10,000 you got in your first deposit, destroying your earned rewards and doing nothing to consolidate the smaller payments. To do this, you need to be able to specify which outputs (which payments received) you want to use to create your transaction; that is what I am going to show you how to accomplish in this guide.
Coin control can also be useful when sending payments from your wallet. By specifying which outputs to use in order to make a payment you can ensure that you are not losing rewards unnecessarily. Please be aware, however, that when sending payments to somebody else you will probably need to send yourself change because each output is used entirely in each transaction. I will explain this properly later on in the guide, but for now just be aware that if you don’t do this you may lose some of your coins.
Manual Coin Control Using the Qt Wallet Console
Manual coin control requires you to use the console rather than the GUI. That means instead of just selecting options from menus, you have to manually type commands. These commands must be precise and use the correct grammar or they won’t work, so please read the instructions carefully and check that you have typed each command correctly before hitting enter.
To open a console window you just need to click ‘Help’ from the navigation menu of your wallet, then select ‘Debug Window’. This will open up a new window with two tabs: click ‘console’ to get to the tab that we are going to use here.
Step One: List Unspent Outputs In your console window type “listunspent” (without the quotation marks) and hit enter. This will give you a list of all the outputs of previous transactions which belong to you, or in more plain language, all of the payments that you have received.
Each one will appear between curly brackets and should look something like this:
{
"txid" : "a long list of random looking characters should be here",
"vout" : "this should be a number",
"address" : "this is the IdealCash address belonging to you that these coins where sent to",
"account" : "",
"scriptPubKey" : "another long list of random looking characters",
"amount" : "the number of coins you received",
"confirmations" : "the number of confirmations for this transaction"
}
You can use this list to select the outputs you want to use to make a payment. For example, IdealCash owners may want to select smaller and newer outputs (newer outputs will have fewer confirmations) and leave any older and larger ones.
When you have chosen which ones you want to use, make a note of the exact “amount” for each one. If you have received coins with more than one address then you will also need a list of each address that appears in one of the outputs you are going to use.
Once you have made a note of these things separately, we only need the “txid”, “vout” and “scriptPubKey” to put into the next step. You may like to copy and paste each one into a text editor and then delete every line apart from those three, to leave something like this:
{
"txid" : "a long list of random looking characters should be here",
"vout" : "this should be a number",
"scriptPubKey" : "another long list of random looking characters"
}
Notice that I have removed the comma from the end of the “scriptPubKey” line. Commas must always be included at the end of each line, apart from the last one. This is one of those annoying grammar things that you have to get right (and which I personally mess up more often than not). Don’t worry too much, if you get this kind of thing wrong you won’t lose any coins, it just won’t accept the command. Also please note that if you are not a programmer then you officially will be after you’ve done this, so feel free to be a bit proud of yourself.
Creating a Raw Transaction
The next step is to use the outputs we have selected to build the code for a complete transaction.
You should have a list of edited outputs from the last section. Put them, complete with brackets, into the command below:
createrawtransaction '[output1, output2]' '{"address you want to send coins to" : number of coins to send}' The number of coins you are sending must be exactly equal to total of all the outputs you have used minus the transaction fee (0.01). It is very important that you get this right as you could lose coins if you make a mistake here. For example, if you have one output with an amount of 1,000 and another with an amount of 2,000 then you must send 2999.99 coins (1000+2000-0.01). If you were to make a mistake and send just 2,000 coins, then you would end up paying a fee of 1,000 coins that you would never see again.
To give you an idea of what this should look you can see an example of a raw bitcoin transaction taken from this Reddit thread below:
createrawtransaction '[{"txid":"c7e5e03d2ab5458819eedec46d0ba38ca7a6525e38b493073277cf4a1550a348","vout":1,"scriptPubKey":"76a9144a06df74729aef1dce5e4641960da3a439d2460b88ac"},
{"txid":"c7e5e03d2ab5458819eedec46d0ba38ca7a6525e38b493073277cf4a1550a348","vout":0,"scriptPubKey":"76a914f88262828f5e64b454249e4c45ddb6071a2ab0a988ac"}]'
'{"Dty3qVvYyggQJnYfaXupbHRAPVhUxr1vso":0.17543376,"DwzkF4gP1xRoFKA4YvJpNFR9qvYzaWrFaE":0.17543375}'
IdealCash and most other altcoins will use the exact same format. In this example you can hopefully see that two addresses are listed to send coins to, with an amount for each one and a comma between them. If you are manually creating a transaction to send coins to somebody else then you will probably need to do this, because you will probably need to select outputs which add up to more than the amount you want to send, and then send the change to yourself. For example, you may have outputs of 10 and 15, but you want to send 20 coins – so you need to send the remaining 5 to your own address, otherwise they will be added to the transaction fee and lost.
When you have pasted this command into the console and hit enter, if you have managed to get all the grammar right, then you will get a long list of random looking characters as a response. This is your ‘raw transaction hex code’. Copy this for use in the next step.
Signing Your Transaction
You now need to sign your transaction with the private keys of all addresses used in the outputs you chose earlier. You can find your private key for any address using the following console command:
dumpprivkey
Obviously, you should replace
with the public address you want to get the private key for. If you have encrypted your wallet then you will need to unlock it before doing this.
You can now sign your raw transaction using the following command:
signrawtransaction 'your hex code generated in the last step' '[output1, output2]' '["privatekeyone", "privatekeytwoifneeded"]'
The middle section with output1 and output2 should be exactly the same as you used in the last step when you created the raw transaction.
When you hit the enter button on that command you will get a new, signed hex code. Copy and paste that into the final command:
Sending Your Transaction
The last bit is easy:
sendrawtransaction 'your signed hex code' When you hit enter on that final command your transaction will be broadcast to the network and your console will reply with a transaction id. If you have used this to send coins to yourself in order to consolidate smaller payments for staking, then your wallet GUI should now show ‘payment to yourself -0.01’.
submitted by Tyler__Z to IdealCash [link] [comments]

Backup Wallet.dat

"1) I can backup my wallet by exporting a wallet.dat file. Do I have to do this everytime I receive more BBP? Or just whenever I add a new key? 2) How do I add new keys? 3) Can I generate and see the private key so that I can write it down/print it and store it somewhere safe?" -znffal
1) think of your wallet.dat file as your passbook in a passbook savings account. You have to have that .dat file to be able to access (and prove you SHOULD have access) to the BBP stored in your account addresses. Exporting it once is all you need.
2) Adding new keys? The passphrase (password) you use is the only "key" you would have in an encrypted wallet (besides the .dat file). If you mean new addresses, you can get those by going under File and Sending (or Receving) Addresses and hit "new".
3) Clicking Encrypt Wallet will be where you choose a passphase, I don't know you can see it other than when you enter it.
To put a real world example or two.
Example One: You don't ever encrypt or backup your wallet. If I borrowed/stole/hacked your computer, I could send all your coins to my wallet (no passphrase).
Example Two: You encrypt your wallet with the passphrase "secret" but don't backup the wallet.dat file, then your computer crashes and you lose all your data. Since you didn't have a copy of the wallet.dat file, your coins would be lost.
Example Three: You backup your wallet.dat but don't encrypt it. Your computer crashes and all your data is lost, but you re-download the QT program, restore your wallet.dat, all your coins are still in you wallet. But if you lose your USB drive that has the wallet.dat on it, and I find it, I can put your wallet.dat on another computer and send all your coins to my wallet.
Example Four: You encrypt your wallet and back up the wallet.dat file. If I hack/borrow your computer, unless I guess your passphrase your coins are safe. If you computer crashes, your can restore your wallet.dat file to another computer and your coins are safe.
In short, Encrypt your wallet (passpharse) and then backup (copy) the wallet.dat file to at least two locations." -616westwarmoth
"Find your wallet.dat file, copy it to a flash drive or any other secure place. If your computer crashes, you'll always have the wallet.dat and can put it on a new machine. It will have to resync a bit when you do, but you'll never lose your "key" to the wallet. Speaking of keys, you should password protect your wallet and make sure to remember it!"
"Yes you must have a copy of the wallet.dat somewhere. So multiple back up copies are a good idea. If you lose the wallet.dat file the coins will be in limbo but there will be no way to recreate the file. One thing to remember is it doesn't matter if the wallet.dat file is "current", it can be 10 years old on a flash drive and you can download a new client, put the wallet.dat file into the machine and you'll be good." -616westwarmoth
"In addition to this, whenever you reboot the node after more than 24 hours of being synced, we back your wallet.dat up into the "backups" folder. This is useful if you ever accidentally delete your wallet.dat.
Also, if you want a paper backup, you can do a 'dumpprivkey accountaddress' command from the RPC." -Rob
"wallet is a collection of private keys"
"there are other ways to achieve high security. You can make a new wallet, encrypt it with a long password, send coins to it, put it on a flash drive and put it in cold storage, then download the hard drive cleaning program and erase the wallet.dat sectors from your PC. And of course, keep a printed copy of the private key on paper and put it in a safe. Put the usb in the safe also. Burn a cd rom with the wallet.dat file and put it in the safe." -Rob
How to safely back up your wallet https://dashpay.atlassian.net/wiki/spaces/DOC/pages/1867878/How+to+safely+back+up+your+wallet
Keep Your Crypto #SAFU (CZ's Tips) https://www.binance.com/en/blog/421499824684900429/Keep-Your-Crypto-SAFU-CZs-Tips
References: https://bitcointalk.org/index.php?topic=2042657.msg23955128#msg23955128 http://forum.biblepay.org/index.php?topic=27.0 https://bitcointalk.org/index.php?topic=2388064.msg27797529#msg27797529
To Read: https://en.bitcoin.it/wiki/Wallet https://en.bitcoin.it/wiki/Storing_bitcoins https://bitcoin.org/en/secure-your-wallet
NOTE: As of version 1.4.3.1 we have updated to HD wallets, so you should not need to worry about keypools anymore if you have upgraded
"Regarding the Sanctuary, you receive payments always to the same address (key), so the keypool is not consumed for those payments. But when you click to generate a new address on the "Receive" tab, one key will be deducted from the keypool. Also, sometimes new addresses are automatically generated and the keypool is consumed, for example when solo mining and finding a block, a new address could be used for the block reward.
You can always check your current keypool size by typing "getwalletinfo" in the RPC console and see "keypoolsize" and "keys_left". It's only concerning if they are a low number and you plan to generate new addresses in your wallet. They start from 1000. If the number gets too low, you can just type "keypoolrefill" to refill them back to 1000 and then you should backup the wallet. But from my experience the wallet automatically refills the keypool from time to time (or after certain actions like transactions), because I see that my wallet file keeps getting larger and the "keys_left" returns to 1000.
The only issue is if you actively use your wallet on multiple computers (for example cloud mining or simply sometimes using the wallet on your laptop), then one wallet could refill the keypool with new addresses and the other one will not, or they will generate different new addresses. If I understand this correctly, for example, you could receive a payment on a new address generated in one wallet; your old balance will be there on both wallets, but only the one wallet where you generated the new address would show the new payment. Then you should copy the wallet.dat file to other computers, to update them.
If you use the wallet on just one computer, you should just backup the wallet from time to time (or when you see it has increased in size). Qt also backups wallet.dat automatically, those can be found in the folder %AppData%\BiblepayCore\backups, you will see that they also have timestamps in their names and possibly different sizes." -inblue
https://bitcointalk.org/index.php?topic=2388064.msg27391534#msg27391534
submitted by togoshige to BiblePay [link] [comments]

A helpful discussion about wallet security (esp. Electrum)

I was recently contacted via private message by a redditor who read a comment of mine about wallet storage (I assume this comment). I think there was quite a bit of useful information in it for other bitcoin beginners, so I am reposting it here in full (with permission). The redditor in question wanted to remain anonymous though.
I hope this is of use to some of you here!
From: Anonymous Redditor
I saw your post regarding your wallet storage and had a few noob questions if you don't mind.
My plan is similar to yours but I was unsure whether to use armory or electrum (electrum's seed creation scares me a bit).
You mentioned you have a bootable LINUX (ubuntu?) USB stick that you keep your wallet on....do you only boot this onto an always offline computer?
Do you use something like Truecrypt to further protect your wallet.dats?
Thanks for your time!
From: SanderMarechal
My plan is similar to yours but I was unsure whether to use armory or electrum (electrum's seed creation scares me a bit).
For me it is the other way around. Armory (and bitcoin-qt) scare me. Armory is just a wallet. It still needs bitcoin-qt running in the background. For me the problem is two-fold:
1) Size
bitcoin-qt (and armory) need to download the entire blockchain. That 13+ GB that takes hours to download and days to verify. And if you ever lose it, you need to do it again.
2) Random keys
armory and bitcoin-qt generate random private keys. You get 100. If you use a few (you use them when you send coins for example) then new ones are created. So, if you create an armory wallet and make a backup, that backup will have 100 keys. Then, if you make 33(!) transactions, your 100 keys are used up and you will have 100 different random keys. If someone then steals your computer (or your house burns down) then you cannot use your backup anymore. It only has the 100 old keys and none of the new keys. So you have lost all your bitcoins.
Why 33 transactions and not 100? Because of change addresses. If you have 10 BTC and send me 2 BTC then most wallets will create 2 transactions. 2 BTC from your old addres to me, and 8 BTC from your old address to a new (random) address. This process costs 3 private keys. 2 keys for the transactions and 1 key to create a new address.
This means that after every few dozen transactions you need to refresh your backup so it has the newer keys. For me that is impractical. It means that I need to keep my backup close by because I often need it.
Electrum does not have this problem. The seed solves this. Private keys are not random but are created from the seed. If you have the seed then you have, by definition, all the private keys you will ever need. Your backup can never be out-of-date. This is easy for me. I save the seed in a file, encrypt it, put it on an USB stick and give copies to a few family members who have safes in their homes.
If my computer is ever stolen, or my house burns down, I can go to a family member, decrypt the seed file and use the seed to restore my electrum wallet. Even if that USB stick is 10 years old.
You mentioned you have a bootable LINUX (ubuntu?) USB stick that you keep your wallet on....do you only boot this onto an always offline computer?
It depends on how secure you want to be. For maximum security, keep the computer always offline. But if you want to spend the bitcoins from your wallet, you will need to be online.
I use the USB stick for my savings account. It only receives coins and I do not send. So I do not need to boot up my USB stick. I have created a second wallet on blockchain.info that I use for day-to-day transactions. All BTC I receive goes to my blockchain account. Then I transfer a part of that to my savings account and only keep a bit of change that I need in the blockchain account.
Do you use something like Truecrypt to further protect your wallet.dats?
No. Electrum does not have a wallet.dat. It has the seed. I simply copy the seed to a TXT file and encrypt it using GPG and symmetric encryption. Example:
gpg --armor --symmetric --cipher-algo AES256 seed.txt 
Make sure you use a password that is strong and that you cannot forget! If you need to write the password down on paper and your house burns down, then you cannot decrypt the seed anymore!
From: Anonymous Redditor
Forgive the naivety here: Correct me if I'm wrong - The safest way to generate your wallet seed is on an offline computer correct? So, theoretically, generate the seed on an offline-only computer, copy to txt...encrypt. back up on multiple USB's. Then on your online computer, load electrum and import Seed?
Thanks so much for the thorough explanation! I'm a potato when it comes to reddit's bitcoin tip bot. Send me an address - would like to send some internet magic money your way.
From: SanderMarechal
The safest way to generate your wallet seed is on an offline computer correct? So, theoretically, generate the seed on an offline-only computer, copy to txt...encrypt. back up on multiple USB's. Then on your online computer, load electrum and import Seed?
Not quite. The risk with an online computer is malware and people breaking in. If you generate the seed on an offline computer and then move it to an online computer, you don't really take that risk away. You still have your wallet on an online computer which you use for day-to-day work and which is exposed to hackers and malware.
I suggest you make two wallets. One wallet is your "savings" wallet. You can use the USB stick Linux for this. Generate the wallet offline, backup and encrypt the seed onto multiple USB sticks and note down the bitcoin address somewhere so you can transfer funds to it. The only time you should use the USB stick to go online is when you want to transfer funds out of your savings wallet.
The, on your normal computer (or your smartphone if you prefer), create a second wallet using a different password. This is the wallet you keep only a little money in for your day-to-day transactions. Note down the seen, encrypt (with a different password than you used to encrypt the seed from your savings wallet) and add it to the USB keys. You can use Electrun for this second wallet as well, but you can also use something different. I use a blockchain.info wallet for my day-to-day expenses.
Whenever you have a larger amount of bitcoins in your day-to-day wallet, transfer some to the wallet on the USB stick. You don't need to boot up the USB stick for this. You only need the address you wrote down.
When you want to spend a large amount of money, boot up from the USB stick and transfer coins from your savings wallet to your day-to-day wallet. Reboot into your normal computer and use the day-to-day wallet to pay for what you wanted to buy.
The core of the issue is simple: Don't store a lot of money in a wallet on a computer that you use a lot. Computers that are used a lot get attacked a lot. Simple :-)
Thanks so much for the thorough explanation! I'm a potato when it comes to reddit's bitcoin tip bot. Send me an address - would like to send some internet magic money your way.
That is very kind! My address is: 1PAXiscvKoGRJ5XxMZvri3CMNeKYYb8wMQ
From: Anonymous Redditor
You are awesome:) Thank you again for the insight! Sent some your way.
From: SanderMarechal*
Your welcome. And thanks for the coin!
From: Anonymous Redditor
Last question(s) (I promise)...
Would a netbook like this be appropriate to 1)dban 2) boot up via USB ubuntu and 3) create the electrum seed?
This would of course never go online, be backed up and encrypted, etc.
http://www.newegg.com/Product/Product.aspx?Item=N82E16834131403
Thanks again.
From: SanderMarechal
I don't know. You would be better off asking this on www.ubuntuforums.org for example. I don't know if that computer's hardware is compatible with Ubuntu. Speed-wise the bottleneck will be the USB stick and not the CPU or memory. USB sticks are much slower than hard drives.
Note that you don't have to buy a computer for this. You can use the computer you already have and still run Ubuntu off an USB stick for your Electrum wallet.
What I said in my previous post about not using your day-to-day computer for your wallet, with that I mean the operating system and software. Not the hardware. Unless you're afraid someone put a hardware keylogger inside your computer :-)
From: Anonymous Redditor
Fascinating!
My tin foil hat is in full effect:) Thanks again for your time and patience.
From: SanderMarechal
Your welcome. Have fun with bitcoin!
Oh, I have a question for you now. Would you mind if I repost our entire private conversation here to /BitcoinBeginners? I think other redditors there would also be interested. And if I can repost it, do you want your username in there or should I replace it with "Anonymous Redditor" or something?
From: Anonymous Redditor
You can certainly repost it! And yes, if you wouldn't mind removing the username I would very much appreciate it.
Thanks for asking btw!
Anyway, I hope this is useful for some people out here.
submitted by SanderMarechal to BitcoinBeginners [link] [comments]

Dash: QT Wallet Encryption = G15E12 How to install a Bitcoin Wallet How To: Encrypt Verge Qt Wallet Bitcoin Wallet Recovery How to get a bitcoin wallet  What is the best bitcoin wallet?  Bitcoin wallet review

You may then encrypt the wallet as desired and make a new backup. 4. Once you've made a new wallet, you can obtain one or more addresses and copy them into a text editor. After obtaining the new address(es), shut down the Bitcoin program, make a backup of the new wallet.dat file and copy it to a new file named wallet-new.dat. 5. Copy the wallet-compromised.dat file back to wallet.dat, start ... This is a project to define a new wallet protocol addressing problems with the current JSON-RPC implementation in bitcoind. Please feel free to make edits. If you disagree with something, turn it into a "debate". Contents. 1 Explanation; 2 Requirements. 2.1 Debates. 2.1.1 Binary or plaintext; 2.1.2 Binary wire formats; 2.1.3 Plaintext wire formats; 2.2 Cooperative mining; 2.3 UI bundling; 3 ... Users will need to encrypt their wallet themselves, though, which may be considered a “daunting task” for novice users. In the end, Bitcoin-QT is a bit of a hit-and-miss among novice cryptocurrency users, thus your mileage may vary. 2. Multibit. Multibit has always advertised itself as the go-to wallet for desktop bitcoin users. It takes ... Often requested feature: encrypt private keys in the wallet.dat file, so a password is required for a send transaction. Bitcoin-Qt could core dump if application initialization failed in certain ways. I double-fixed this: 1) qt/bitcoin.cpp now shuts down core threads cleanly if AppInit2 returns false 2) init.cpp now exits before StartNode() if strErrors is set (no reason to StartNode if we're just going to exit immediately anyway). Tested by triggering all of the various ways AppInit2 can fail, either by ...

[index] [49119] [361] [49404] [16182] [2302] [50053] [15294] [51541] [46920] [7725]

Dash: QT Wallet Encryption = G15E12

Episode 1 : Bitcoin Series In this video I teach you how to install a digital wallet to contain your Bitcoins. I also teach you how to utilize the Bitcoin Faucet to get your first free coin. In this video from http://www.secureyourwallet.com we do a full review of the original Satoshi Bitcoin wallet. We do an install, look at the blockchain data,... How to be your own bank! Encrypt, Back up, & Restore Bitcoin (BTC) wallet! Run a Full Node! - Duration: 25:34. Coin Decrypt 177 views But the Bitcoin plan calls for the creation of only 21 million bitcoins. In this way, Bitcoin will try to avoid the pitfalls of modern fiat currencies such as inflation, deflation, market ... - Click settings top left of screen. - Select 'Encrypt Wallet' and follow instructions. To support me you can donate $XVG address: DQoFGdaRCMkwAqbTB7fUwN4GBrdN5Ao53c.

#