json rpc - How to install a Bitcoin client on Ubuntu ...

Gridcoin 5.0.0.0-Mandatory "Fern" Release

https://github.com/gridcoin-community/Gridcoin-Research/releases/tag/5.0.0.0
Finally! After over ten months of development and testing, "Fern" has arrived! This is a whopper. 240 pull requests merged. Essentially a complete rewrite that was started with the scraper (the "neural net" rewrite) in "Denise" has now been completed. Practically the ENTIRE Gridcoin specific codebase resting on top of the vanilla Bitcoin/Peercoin/Blackcoin vanilla PoS code has been rewritten. This removes the team requirement at last (see below), although there are many other important improvements besides that.
Fern was a monumental undertaking. We had to encode all of the old rules active for the v10 block protocol in new code and ensure that the new code was 100% compatible. This had to be done in such a way as to clear out all of the old spaghetti and ring-fence it with tightly controlled class implementations. We then wrote an entirely new, simplified ruleset for research rewards and reengineered contracts (which includes beacon management, polls, and voting) using properly classed code. The fundamentals of Gridcoin with this release are now on a very sound and maintainable footing, and the developers believe the codebase as updated here will serve as the fundamental basis for Gridcoin's future roadmap.
We have been testing this for MONTHS on testnet in various stages. The v10 (legacy) compatibility code has been running on testnet continuously as it was developed to ensure compatibility with existing nodes. During the last few months, we have done two private testnet forks and then the full public testnet testing for v11 code (the new protocol which is what Fern implements). The developers have also been running non-staking "sentinel" nodes on mainnet with this code to verify that the consensus rules are problem-free for the legacy compatibility code on the broader mainnet. We believe this amount of testing is going to result in a smooth rollout.
Given the amount of changes in Fern, I am presenting TWO changelogs below. One is high level, which summarizes the most significant changes in the protocol. The second changelog is the detailed one in the usual format, and gives you an inkling of the size of this release.

Highlights

Protocol

Note that the protocol changes will not become active until we cross the hard-fork transition height to v11, which has been set at 2053000. Given current average block spacing, this should happen around October 4, about one month from now.
Note that to get all of the beacons in the network on the new protocol, we are requiring ALL beacons to be validated. A two week (14 day) grace period is provided by the code, starting at the time of the transition height, for people currently holding a beacon to validate the beacon and prevent it from expiring. That means that EVERY CRUNCHER must advertise and validate their beacon AFTER the v11 transition (around Oct 4th) and BEFORE October 18th (or more precisely, 14 days from the actual date of the v11 transition). If you do not advertise and validate your beacon by this time, your beacon will expire and you will stop earning research rewards until you advertise and validate a new beacon. This process has been made much easier by a brand new beacon "wizard" that helps manage beacon advertisements and renewals. Once a beacon has been validated and is a v11 protocol beacon, the normal 180 day expiration rules apply. Note, however, that the 180 day expiration on research rewards has been removed with the Fern update. This means that while your beacon might expire after 180 days, your earned research rewards will be retained and can be claimed by advertising a beacon with the same CPID and going through the validation process again. In other words, you do not lose any earned research rewards if you do not stake a block within 180 days and keep your beacon up-to-date.
The transition height is also when the team requirement will be relaxed for the network.

GUI

Besides the beacon wizard, there are a number of improvements to the GUI, including new UI transaction types (and icons) for staking the superblock, sidestake sends, beacon advertisement, voting, poll creation, and transactions with a message. The main screen has been revamped with a better summary section, and better status icons. Several changes under the hood have improved GUI performance. And finally, the diagnostics have been revamped.

Blockchain

The wallet sync speed has been DRASTICALLY improved. A decent machine with a good network connection should be able to sync the entire mainnet blockchain in less than 4 hours. A fast machine with a really fast network connection and a good SSD can do it in about 2.5 hours. One of our goals was to reduce or eliminate the reliance on snapshots for mainnet, and I think we have accomplished that goal with the new sync speed. We have also streamlined the in-memory structures for the blockchain which shaves some memory use.
There are so many goodies here it is hard to summarize them all.
I would like to thank all of the contributors to this release, but especially thank @cyrossignol, whose incredible contributions formed the backbone of this release. I would also like to pay special thanks to @barton2526, @caraka, and @Quezacoatl1, who tirelessly helped during the testing and polishing phase on testnet with testing and repeated builds for all architectures.
The developers are proud to present this release to the community and we believe this represents the starting point for a true renaissance for Gridcoin!

Summary Changelog

Accrual

Changed

Most significantly, nodes calculate research rewards directly from the magnitudes in EACH superblock between stakes instead of using a two- or three- point average based on a CPID's current magnitude and the magnitude for the CPID when it last staked. For those long-timers in the community, this has been referred to as "Superblock Windows," and was first done in proof-of-concept form by @denravonska.

Removed

Beacons

Added

Changed

Removed

Unaltered

As a reminder:

Superblocks

Added

Changed

Removed

Voting

Added

Changed

Removed

Detailed Changelog

[5.0.0.0] 2020-09-03, mandatory, "Fern"

Added

Changed

Removed

Fixed

submitted by jamescowens to gridcoin [link] [comments]

"No peers"

Hi there, i've recently.started using wasabi, made a wallet and transfered some money without issue the first time I used it.
Now I try to access my wallet to transfer some.bitcoin but I cannot seem to connect properly.
It took a while but finally downloaded all filters, it connects to tor, backend and shows price of btc but can't seem to find any peers, log doesn't show any error for both tor nor general log afaik.
I'm using linux mint (ubuntu) on its latest iteration and downloaded wasabi client from their domain 2 days ago so it should be updated, any ideas on what may be going on?
submitted by JasperDaly to WasabiWallet [link] [comments]

Bitcoin Cash Node Ubuntu PPA repository is available

The Bitcoin Cash Node Ubuntu PPA repository has been set up to serve version 0.21.0 and is available at:
 
https://launchpad.net/~bitcoin-cash-node/+archive/ubuntu/ppa
 
To install
 
sudo add-apt-repository ppa:bitcoin-cash-node/ppa sudo apt-get update sudo apt install bitcoind bitcoin-qt 
 
NB if you have installed other Bitcoin Cash clients via PPA, it would be better to uninstall those binaries and remove their repository, eg:
 
sudo apt-get remove bitcoind bitcoin-qt bitcoin-tx sudo add-apt-repository --remove ppa:bitcoin-abc/ppa 
submitted by s1ckpig to btc [link] [comments]

BCH Unlimited Ubuntu PPA repo updated to version 1.8.0

The BCH Unlimited Ubuntu PPA repository has been updated to serve version 1.8.0 is available at:
 
https://launchpad.net/~bitcoin-unlimited/+archive/ubuntu/bucash
 
This release is compatible the Bitcoin Cash protocol. To update already installed packages (*):
 
sudo apt update sudo apt upgrade 
 
To install
 
sudo add-apt-repository ppa:bitcoin-unlimited/bucash sudo apt-get update sudo apt install bitcoind bitcoin-qt 
 
starting from this update the repository is serving also ElectrsCash(**) v.1.1.1, for now just for the amd64 architecture. To install it just execute this command:
sudo apt install electrscash 
 
See the official announcement and the release notes for more details:
https://np.reddit.com/btc/comments/g3k4mbch_unlimited_180_has_just_been_released/
https://github.com/BitcoinUnlimited/BitcoinUnlimited/blob/release/doc/release-notes/release-notes-1.8.0.md
 
Known issues:
On Ubuntu 18.04 (bionic) you'll probably get an error while trying to install bitcoind. The error message is the following:
The following packages have unmet dependencies. bitcoind : Depends: libgcc-s1 (>= 3.4) but it is not installable E: Unable to correct problems, you have held broken packages. Package libgcc-s1 is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source 
It seems like libgcc-s1 which is a focal (ubuntu 20.04, still in beta) package that has somehow crept in the bionic "food-chain", I'm working on a fix right now. Thanks to xd1gital for the initial report.
Edit: to solve the problem please do:
sudo add-apt-repository ppa:ubuntu-toolchain-test sudo apt update sudo apt dist-upgrade sudo apt install bitcoind 
 
(*) due to fact we rebranded Ubuntua PPA name along with the name of the clients, you will be displayed with this warning and question to which you could safely reply "Yes":
E: Repository 'http://ppa.launchpad.net/bitcoin-unlimited/bucash/ubuntu bionic InRelease' changed its 'Label' value from 'BU Cash' to 'BCH Unlimited' N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details. Do you want to accept these changes and continue updating from this repository? [y/N] 
  (**) ElectrsCash is an efficient re-implementation of Electrum Server written in Rust.
submitted by s1ckpig to bitcoin_unlimited [link] [comments]

BCH Unlimited Ubuntu PPA repo updated to version 1.8.0

The BCH Unlimited Ubuntu PPA repository has been updated to serve version 1.8.0 is available at:
 
https://launchpad.net/~bitcoin-unlimited/+archive/ubuntu/bucash
 
This release is compatible the Bitcoin Cash protocol. To update already installed packages (*):
 
sudo apt update sudo apt upgrade 
 
To install
 
sudo add-apt-repository ppa:bitcoin-unlimited/bucash sudo apt-get update sudo apt install bitcoind bitcoin-qt 
 
starting from this update the repository is serving also ElectrsCash(**) v.1.1.1, for now just for the amd64 architecture. To install it just execute this command:
sudo apt install electrscash 
 
See the official announcement and the release notes for more details:
https://np.reddit.com/btc/comments/g3k4mbch_unlimited_180_has_just_been_released/
https://github.com/BitcoinUnlimited/BitcoinUnlimited/blob/release/doc/release-notes/release-notes-1.8.0.md
 
Known issues:
On Ubuntu 18.04 (bionic) you'll probably get an error while trying to install bitcoind. The error message is the following:
The following packages have unmet dependencies. bitcoind : Depends: libgcc-s1 (>= 3.4) but it is not installable E: Unable to correct problems, you have held broken packages. Package libgcc-s1 is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source 
It seems like libgcc-s1 which is a focal (ubuntu 20.04, still in beta) package that has somehow crept in the bionic "food-chain", I'm working on a fix right now. Thanks to xd1gital for the initial report.
Edit: to solve the problem please do:
sudo add-apt-repository ppa:ubuntu-toolchain-test sudo apt update sudo apt dist-upgrade sudo apt install bitcoind 
 
(*) due to fact we rebranded Ubuntua PPA name along with the name of the clients, you will be displayed with this warning and question to which you could safely reply "Yes":
E: Repository 'http://ppa.launchpad.net/bitcoin-unlimited/bucash/ubuntu bionic InRelease' changed its 'Label' value from 'BU Cash' to 'BCH Unlimited' N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details. Do you want to accept these changes and continue updating from this repository? [y/N] 
  (**) ElectrsCash is an efficient re-implementation of Electrum Server written in Rust.
submitted by s1ckpig to btc [link] [comments]

BCH Unlimited Ubuntu PPA repo updated to version 1.8.0

The BCH Unlimited Ubuntu PPA repository has been updated to serve version 1.8.0 is available at:

 

https://launchpad.net/~bitcoin-unlimited/+archive/ubuntu/bucash

 

This release is compatible the Bitcoin Cash protocol. To update already installed packages (*):

 

sudo apt update
sudo apt upgrade

 

To install

 

sudo add-apt-repository ppa:bitcoin-unlimited/bucash
sudo apt-get update
sudo apt install bitcoind bitcoin-qt

 

starting from this update the repository is serving also ElectrsCash(**) v.1.1.1, for now just for the `amd64` architecture. To install it just execute this command:

sudo apt install electrscash

 

See the official announcement and the release notes for more details:

https://np.reddit.com/btc/comments/g3k4mbch_unlimited_180_has_just_been_released/

https://github.com/BitcoinUnlimited/BitcoinUnlimited/blob/release/doc/release-notes/release-notes-1.8.0.md

 

Known issues:

On Ubuntu 18.04 (bionic) you'll probably get an error while trying to install `bitcoind`. The error message is the following:

The following packages have unmet dependencies.
bitcoind : Depends: libgcc-s1 (>= 3.4) but it is not installable
E: Unable to correct problems, you have held broken packages.

Package libgcc-s1 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

It seems like [libgcc-s1](https://packages.ubuntu.com/focal/libgcc-s1) which is a focal (ubuntu 20.04, still in beta) package that has somehow crept in the bionic "food-chain", I'm working on a fix right now. Thanks to xd1gital for the initial report.

 

(*) due to fact we rebranded Ubuntua PPA name along with the name of the clients, you will be displayed with this warning and question to which you could safely reply "Yes":

E: Repository 'http://ppa.launchpad.net/bitcoin-unlimited/bucash/ubuntu bionic InRelease' changed its 'Label' value from 'BU Cash' to 'BCH Unlimited'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
Do you want to accept these changes and continue updating from this repository? [y/N]

 
(**) ElectrsCash is an efficient re-implementation of Electrum Server written in Rust.
submitted by s1ckpig to Bitcoincash [link] [comments]

Groestlcoin 6th Anniversary Release

Introduction

Dear Groestlers, it goes without saying that 2020 has been a difficult time for millions of people worldwide. The groestlcoin team would like to take this opportunity to wish everyone our best to everyone coping with the direct and indirect effects of COVID-19. Let it bring out the best in us all and show that collectively, we can conquer anything.
The centralised banks and our national governments are facing unprecedented times with interest rates worldwide dropping to record lows in places. Rest assured that this can only strengthen the fundamentals of all decentralised cryptocurrencies and the vision that was seeded with Satoshi's Bitcoin whitepaper over 10 years ago. Despite everything that has been thrown at us this year, the show must go on and the team will still progress and advance to continue the momentum that we have developed over the past 6 years.
In addition to this, we'd like to remind you all that this is Groestlcoin's 6th Birthday release! In terms of price there have been some crazy highs and lows over the years (with highs of around $2.60 and lows of $0.000077!), but in terms of value– Groestlcoin just keeps getting more valuable! In these uncertain times, one thing remains clear – Groestlcoin will keep going and keep innovating regardless. On with what has been worked on and completed over the past few months.

UPDATED - Groestlcoin Core 2.18.2

This is a major release of Groestlcoin Core with many protocol level improvements and code optimizations, featuring the technical equivalent of Bitcoin v0.18.2 but with Groestlcoin-specific patches. On a general level, most of what is new is a new 'Groestlcoin-wallet' tool which is now distributed alongside Groestlcoin Core's other executables.
NOTE: The 'Account' API has been removed from this version which was typically used in some tip bots. Please ensure you check the release notes from 2.17.2 for details on replacing this functionality.

How to Upgrade?

Windows
If you are running an older version, shut it down. Wait until it has completely shut down (which might take a few minutes for older versions), then run the installer.
OSX
If you are running an older version, shut it down. Wait until it has completely shut down (which might take a few minutes for older versions), run the dmg and drag Groestlcoin Core to Applications.
Ubuntu
http://groestlcoin.org/forum/index.php?topic=441.0

Other Linux

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

Download

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

Source

ALL NEW - Groestlcoin Moonshine iOS/Android Wallet

Built with React Native, Moonshine utilizes Electrum-GRS's JSON-RPC methods to interact with the Groestlcoin network.
GRS Moonshine's intended use is as a hot wallet. Meaning, your keys are only as safe as the device you install this wallet on. As with any hot wallet, please ensure that you keep only a small, responsible amount of Groestlcoin on it at any given time.

Features

Download

iOS
Android

Source

ALL NEW! – HODL GRS Android Wallet

HODL GRS connects directly to the Groestlcoin network using SPV mode and doesn't rely on servers that can be hacked or disabled.
HODL GRS utilizes AES hardware encryption, app sandboxing, and the latest security features to protect users from malware, browser security holes, and even physical theft. Private keys are stored only in the secure enclave of the user's phone, inaccessible to anyone other than the user.
Simplicity and ease-of-use is the core design principle of HODL GRS. A simple recovery phrase (which we call a Backup Recovery Key) is all that is needed to restore the user's wallet if they ever lose or replace their device. HODL GRS is deterministic, which means the user's balance and transaction history can be recovered just from the backup recovery key.

Features

Download

Main Release (Main Net)
Testnet Release

Source

ALL NEW! – GroestlcoinSeed Savior

Groestlcoin Seed Savior is a tool for recovering BIP39 seed phrases.
This tool is meant to help users with recovering a slightly incorrect Groestlcoin mnemonic phrase (AKA backup or seed). You can enter an existing BIP39 mnemonic and get derived addresses in various formats.
To find out if one of the suggested addresses is the right one, you can click on the suggested address to check the address' transaction history on a block explorer.

Features

Live Version (Not Recommended)

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

Download

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

Source

ALL NEW! – Vanity Search Vanity Address Generator

NOTE: NVidia GPU or any CPU only. AMD graphics cards will not work with this address generator.
VanitySearch is a command-line Segwit-capable vanity Groestlcoin address generator. Add unique flair when you tell people to send Groestlcoin. Alternatively, VanitySearch can be used to generate random addresses offline.
If you're tired of the random, cryptic addresses generated by regular groestlcoin clients, then VanitySearch is the right choice for you to create a more personalized address.
VanitySearch is a groestlcoin address prefix finder. If you want to generate safe private keys, use the -s option to enter your passphrase which will be used for generating a base key as for BIP38 standard (VanitySearch.exe -s "My PassPhrase" FXPref). You can also use VanitySearch.exe -ps "My PassPhrase" which will add a crypto secure seed to your passphrase.
VanitySearch may not compute a good grid size for your GPU, so try different values using -g option in order to get the best performances. If you want to use GPUs and CPUs together, you may have best performances by keeping one CPU core for handling GPU(s)/CPU exchanges (use -t option to set the number of CPU threads).

Features

Usage

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

Download

Source

ALL NEW! – Groestlcoin EasyVanity 2020

Groestlcoin EasyVanity 2020 is a windows app built from the ground-up and makes it easier than ever before to create your very own bespoke bech32 address(es) when whilst not connected to the internet.
If you're tired of the random, cryptic bech32 addresses generated by regular Groestlcoin clients, then Groestlcoin EasyVanity2020 is the right choice for you to create a more personalised bech32 address. This 2020 version uses the new VanitySearch to generate not only legacy addresses (F prefix) but also Bech32 addresses (grs1 prefix).

Features

Download

Source

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

Groestlcoin WPF is an alternative full node client with optional lightweight 'thin-client' mode based on WPF. Windows Presentation Foundation (WPF) is one of Microsoft's latest approaches to a GUI framework, used with the .NET framework. Its main advantages over the original Groestlcoin client include support for exporting blockchain.dat and including a lite wallet mode.
This wallet was previously deprecated but has been brought back to life with modern standards.

Features

Remastered Improvements

Download

Source

ALL NEW! – BIP39 Key Tool

Groestlcoin BIP39 Key Tool is a GUI interface for generating Groestlcoin public and private keys. It is a standalone tool which can be used offline.

Features

Download

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

Source

ALL NEW! – Electrum Personal Server

Groestlcoin Electrum Personal Server aims to make using Electrum Groestlcoin wallet more secure and more private. It makes it easy to connect your Electrum-GRS wallet to your own full node.
It is an implementation of the Electrum-grs server protocol which fulfils the specific need of using the Electrum-grs wallet backed by a full node, but without the heavyweight server backend, for a single user. It allows the user to benefit from all Groestlcoin Core's resource-saving features like pruning, blocks only and disabled txindex. All Electrum-GRS's feature-richness like hardware wallet integration, multi-signature wallets, offline signing, seed recovery phrases, coin control and so on can still be used, but connected only to the user's own full node.
Full node wallets are important in Groestlcoin because they are a big part of what makes the system be trust-less. No longer do people have to trust a financial institution like a bank or PayPal, they can run software on their own computers. If Groestlcoin is digital gold, then a full node wallet is your own personal goldsmith who checks for you that received payments are genuine.
Full node wallets are also important for privacy. Using Electrum-GRS under default configuration requires it to send (hashes of) all your Groestlcoin addresses to some server. That server can then easily spy on your transactions. Full node wallets like Groestlcoin Electrum Personal Server would download the entire blockchain and scan it for the user's own addresses, and therefore don't reveal to anyone else which Groestlcoin addresses they are interested in.
Groestlcoin Electrum Personal Server can also broadcast transactions through Tor which improves privacy by resisting traffic analysis for broadcasted transactions which can link the IP address of the user to the transaction. If enabled this would happen transparently whenever the user simply clicks "Send" on a transaction in Electrum-grs wallet.
Note: Currently Groestlcoin Electrum Personal Server can only accept one connection at a time.

Features

Download

Windows
Linux / OSX (Instructions)

Source

UPDATED – Android Wallet 7.38.1 - Main Net + Test Net

The app allows you to send and receive Groestlcoin on your device using QR codes and URI links.
When using this app, please back up your wallet and email them to yourself! This will save your wallet in a password protected file. Then your coins can be retrieved even if you lose your phone.

Changes

Download

Main Net
Main Net (FDroid)
Test Net

Source

UPDATED – Groestlcoin Sentinel 3.5.06 (Android)

Groestlcoin Sentinel is a great solution for anyone who wants the convenience and utility of a hot wallet for receiving payments directly into their cold storage (or hardware wallets).
Sentinel accepts XPUB's, YPUB'S, ZPUB's and individual Groestlcoin address. Once added you will be able to view balances, view transactions, and (in the case of XPUB's, YPUB's and ZPUB's) deterministically generate addresses for that wallet.
Groestlcoin Sentinel is a fork of Groestlcoin Samourai Wallet with all spending and transaction building code removed.

Changes

Download

Source

UPDATED – P2Pool Test Net

Changes

Download

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

Source

submitted by Yokomoko_Saleen to groestlcoin [link] [comments]

How to get a public static ip for your local lightning node

My lightning node is a node that is running locally on my server hardware in my house down under, far from the New Jersey Digitalocean datacenter, which is what will come up if you look up the ip of the node. This is done via an OpenVPN tunnel from your local machine to a VPS. I am doing this by renting a VPS from Digitalocean for $20 a month (2 vCPUs, 2GB RAM) running Ubuntu 18.04. You can do this just as easily on a $5 a month VPS with 1 vCPU and 1GB RAM or even a $2.50 a month VPS from Vultr with 512MB RAM. I needed the extra power because I have many web services running there as well.
This setup allows me to have a highly available lightning node, not affected by my home IP address changing. If you are using a mobile connection or have a CGNAT, you wont be able to port forward for your lightning node. This setup allows you to do so. You can also use this to make a portable lightning node, which can get you a full lightning node wherever you have power and internet, without having to mess with network settings. If you don't want others to know your home IP, this is a good option for privacy.
  1. Setup a local lightning node, preferably on a linux machine. I followed the Raspibolt tu`ial (with some tweaks) on a 2 vCPU and 8GB RAM VM running Ubuntu 16.04.
  2. Get a VPS with a static IP address. Digitalocean and Vultr VPSs already are. This VPS wont need much power, so get the cheapest one you can.
  3. Secure the VPS. I used this tutorial. Essentially, setup a non root user, use ssh keys, and setup ufw. Also make sure to allow port 9735 through ufw for lightning. I also additionally made adjustments to the ssh config and installed fail2ban.
  4. Setup an OpenVPN server on the VPS. I used this tutorial.
  5. Install on OpenVPN client on the local linux machine and connect to the server. The tutorial from step 4 shows how to this. Keep this connected for step 6.
  6. SSH into the VPS and figure out the OpenVPN IP address of the client. It should be 10.8.0.x. To figure out the x, setup a simple python web server or something on the local machine on port 8000 or something and open the port on ufw in the local machine. Keep the OpenVPN connection, and use a new ssh session when accessing your local machine. Don't kill the OpenVPN connection, as it may complicate things when finding the ip.
    mkdir testweb
    cd testweb
    echo hello >> index.html
    sudo ufw allow 8000
    python -m SimpleHTTPServer 8000
  7. SSH back into the VPS. Run the curl command below, and try all the numbers between 2-10 for x. When you get hello as your output, then you found the right IP. I found mine at 6. You may have to try higher numbers, but this is unlikely. You can kill your python webserver on your local machine once you find it.
    curl 10.8.0.x:8000
  8. Once you have the IP, you want to make this static, so it doesn't change when you reconnect. This is done on the VPS side, so ssh back into the VPS. This tutorial worked for me. Just make sure to change values like the CommonName and and the IP to match yours (client1 and 10.8.0.x). If it doesn't work search "make openvpn ip static" and look around.
  9. SSH into your local machine, and make the OpenVPN connection persistent. You can kill the OpenVPN connection now. Doing this and this worked for me. If it doesn't work search "openvpn keepalive" or "openvpn auto connect linux" or "make openvpn connection persistent linux".
  10. Restart your local machine, and make sure it connects on boot. Do the python webserver test again, and make sure the same ip is shown on the VPS, and it is still accessible.
  11. SSH back into the VPS. Now, you have to port forward with iptables. you have to add the 2 lines below starting with -A PREROUTING in the same place in your /etc/ufw/before.rules file. Here is what mine looks like. Change the x to your OpenVPN IP. Do sudo ufw disable and sudo ufw enable to restart ufw to update your changes.
    *nat
    :POSTROUTING ACCEPT [0:0]
    -A PREROUTING -i eth0 -p tcp -m tcp --dport 9735 -j DNAT --to-destination 10.8.0.x:9735
    -A PREROUTING -i eth0 -p udp -m udp --dport 9735 -j DNAT --to-destination 10.8.0.x:9735
    -A POSTROUTING -s 10.8.0.0/8 -o eth0 -j MASQUERADE
    COMMIT
  12. SSH into your local machine. Change your lnd.conf to match with this setup, like changing the externalip. Here is what my config looks like, a slight tweak from the Raspibolt one:
    [Application Options]
    debuglevel=info
    maxpendingchannels=5
    alias=GCUBED [LND]
    color=#68F442
    listen=0.0.0.0:9735
    externalip=157.230.95.74:9735
    [Bitcoin]
    bitcoin.active=1
    bitcoin.mainnet=1
    bitcoin.node=bitcoind
    [autopilot]
    autopilot.active=1
    autopilot.maxchannels=5
    autopilot.allocation=0.6
  13. Do a sudo service lnd restart to restart lnd and apply the changes. Remember to do a lncli unlock after any restarts. Your lnd node should now have a public static ip. Look it up a few hours after you do this on 1ml, your ip should be the one of your VPS now.
I am monitoring this for free with uptimerobot. It will notify you if it has gone down. So far mine has been running for 3 days and hasn't gone down.
EDIT: Formatting
EDIT 2: The main reason I didn't use a ddns or a hidden service was mainly for high uptime, and low latency. I am planning on developing a lapp with this node and I didn't want to risk any downtime. Running lightning as a hidden service is a great idea as well, this tutorial shows how to achieve something similar with the clearnet.
EDIT 3: You can achieve a similar result from using TOR
submitted by ggelango to Bitcoin [link] [comments]

Bitcoin Unlimited - Bitcoin Cash edition 1.5.0.1 has just been released

Download the latest Bitcoin Cash compatible release of Bitcoin Unlimited (1.5.0.1, November 5th, 2018) from:
 
https://www.bitcoinunlimited.info/download
 
This release is a major release which is compatible with the Bitcoin Cash compatible with the Bitcoin Cash specifications you could find here:
This release will also implement a set of consensus changes proposed by an alternative implementation, Bitcoin SV, see SV release notes for ver 0.1.0 for more details. Such set of features is disabled by default, the default policy is to activate the set of changes as defined by the bitcoincash.org specification.
To configure your BUcash client so that it will activate the protocol upgrade proposed by SV you need to add consensus.forkNov2018Time=0 and consensus.svForkNov2018Time=1 in your bitcoin.conf file. Trying to activate both protocol upgrades at the same time will lead to the client to exit with this error message: Both the SV and ABC forks are enabled. You must choose one.
List of notable changes and fixes to the code base:
 
Release notes: https://github.com/BitcoinUnlimited/BitcoinUnlimited/blob/dev/doc/release-notes/release-notes-bucash1.5.0.1.md
 
PS:
submitted by s1ckpig to btc [link] [comments]

Ethereum on ARM. Geth and Parity clients update. Status.im, IPFS and Swarm packages. Raiden Network and Trinity client installers.

EthArmbian [1] is a custom Linux image for the NanoPC-T4 ARM SoC [2] that runs Geth or Parity Ethereum clients as a boot service and automatically turns the device into a full Ethereum node.
Once powered up, the image takes care of all steps, from setting up the environment to running the Ethereum client and synchronizing the blockchain.
Edit: Images links are now Ready for Constantinople and Petersburg Hardforks. You can update Geth to 1.8.22 and Parity to 2.2.9 from these images by running:
update-ethereum
This is a new release of the EthArmbian image for the NanoPC-T4 ARM board. Ethereum is evolving quickly so it is time to include some other interesting pieces of the ecosystem. Changelog:

Download links

Armbian_5.74_Nanopct4_Ubuntu_bionic_default_4.4.172-1-geth.img.zip
Armbian_5.74_Nanopct4_Ubuntu_bionic_default_4.4.172-1-parity.img.zip
Note: The only difference between both images is the default client that runs at boot time. You can switch between Geth or Parity at anytime.
For further info regarding installation and usage please visit Github README [1]

Status.im, IPFS and Swarm

Status [5] is a decentralized messaging & browsing app (using the Whisper protocol). And as any P2P system, it needs… peers. So if you want to support it, status is now included as a systemd service, configured in whisper and mailserver mode.
You need to start it manually as it doesn’t run by default:
sudo systemctl start status.im
And, if you want it to get started on boot you need:
sudo systemctl enable status.im
Configuration options are located in /etc/ethereum/status.im.json.
Why run a Status node? (from their FAQ):
Currently, we don’t provide any incentives for running Status Nodes. We are working hard to solve this problem. Our intent is to increase the size of the Whisper network, thereby improving how “decentralized” and safe our platform is.
Another reason is privacy. In the current setup, nodes that are running as Mail Servers are trusted. This means that such a node can communicate directly with the Status app using a p2p connection and some metadata might leak. If one wants to avoid that, the best option is to run a Mail Server on your own and configure it in the Status app.
Another important piece of the so called web 3 is decentralized storage. The most mature option available is IPFS [6] which is now included as a systemd service as well. You need to start it manually as it doesn’t run for default:
sudo systemctl start ipfs
If you want IPFS to get started on boot you need to enable it by running:
sudo systemctl enable ipfs
You can tweak config options in /home/ethereum/.ipfs/config file (particularly, you may want to adjust the StorageMax parameter).
Swarm [7] (Ethereum decentralized storage solution) is available as a binary. You may want to take a look at the official docs to start testing it.
You can run these clients along with Geth or Parity client with no performance issues.

Raiden and Trinity

As you may know, Raiden Network [8] is a Layer 2 scalability solution (similar to Bitcoin's Lightning Network). Trinity [9] is a new Ethereum client developed entirely in Python (and already working on the beacon chain).
You can install both clients by running its corresponding bash script. Take into account that both are in alpha stage so expect some trouble and give back feedback to developers, if possible. They are not properly packaged yet so the script installs them directly from Github (it takes a while).
Installation: Type (as ethereum user):
install-trinity
install-raiden
You can now run "trinity" or "raiden" commands.
Note on Trinity: If you experience this issue: “trinity: error: Timed out waiting for database start”, try to increase wait_for_ipc() “timeout” value in /uslocal/lib/python3.6/dist-packages/trinity/utils/ipc.py [10]

Ethereum nodes FUD

We’ve been seeing lately a lot of misinformation about Ethereum blockchain size and other kind of FUD.
Stick to the facts. With Parity, it just takes several hours to get a full node up and running and you need about 140 GB of SSD disk size (2-3 days with Geth and 150GB of disk size). So, you could run a full node for several months even with a 256GB SSD unit. Don’t listen to this kind of nonsense. Plain and simple: they are wrong.
This "guy" knows [11]

References

[1] https://github.com/diglos/userpatches
[2] https://www.friendlyarm.com/index.php?route=product/product&product_id=225
[3] https://github.com/ethereum/go-ethereum/releases/tag/v1.8.21
[4] https://github.com/paritytech/parity-ethereum/releases/tag/v2.2.7
[5] https://status.im/
[6] https://ipfs.io/
[7] https://swarm-guide.readthedocs.io/en/latest/introduction.html
[8] https://raiden.network/
[9] https://trinity.ethereum.org/
[10] https://github.com/ethereum/trinity/issues/182
https://github.com/ethereum/trinity/pull/192/commits/e19326689cbb08fd81c1827a7a3ab41200bbbeff
[11] https://twitter.com/ethnodesize
submitted by diglos76 to ethereum [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]

Bitcoin foundation should add a ppa for Ubuntu 14.04 (trusty). I have ubuntu and still have the heartbleed vulnerable 0.9.0 version of Bitcoin Core.

submitted by daf121 to Bitcoin [link] [comments]

Bitcoin Unlimited Cash edition 1.1.1.0 has just been released

Download the latest Bitcoin Cash compatible release of Bitcoin Unlimited (1.1.1.0, August 10, 2017) from:
https://www.bitcoinunlimited.info/download
Notable changes:
Release notes: https://github.com/BitcoinUnlimited/BitcoinUnlimited/blob/BitcoinCash/doc/release-notes/release-notes-bucash1.1.1.0.md
NOTE: This release is for Bitcoin Cash, a FORK of Bitcoin happened on Aug 1,2017! If you are new to Bitcoin or do not understand the prior sentence, you do not want this release. Instead choose the "Latest Official Release".
Ubuntu PPA is in the process of being updated.
submitted by s1ckpig to btc [link] [comments]

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

This tutorial has been updated: https://www.reddit.com/reddCoin/comments/a0wn1v/updated_staking_reddcoin_core_client_gui_wallet/.
   

Intro

I want to stake Reddcoins on my Raspberry Pi, but there is no easy to install package for the Reddcoin Core client. I found some tutorials (mentioned at the bottom, under 'credits'), but I still struggled to get the result I wanted. It took some small adjustments, but I got the GUI Wallet of Reddcoin Core working on my Raspberry Pi Model 3B. See the steps below. :).
 
If you have any questions or comments, please post a comment in this thread, so others can also benefit from it.
 
If you would like to tip me: RqvdnNX5MTam855Y2Vudv7yVgtXdcYaQAW.
   
Even though Raspbian is the primary OS for the Raspberry Pi, it seems that it's not possible to build and compile the Reddcoin wallet software for Raspbian Stretch. However, I got the wallet compiled using Ubuntu MATE.
     

Overview

     

Steps

 
 
 
 
 
 
 
 
 
 
 
 
 
 
     

Extra

 
 
 
 
     

Credits:

 
Thank you all for sharing your knowledge!
submitted by Yavuz_Selim to reddCoin [link] [comments]

Lightning node on Windows - testing, get not connected

Ok after testing BTCPay, C-Lightning, LND on Ubuntu I said ok let's try also the Windows implementation, is just few clicks and done (as it is promoted).
So I followed this github guide that actually send you to this one.
OK, started Bitcoin-core client on Windows 7 x64, with an already synced data folder. Empty bitcoin.conf (none of guides says how to configure the conf file). Wait until the client is full synced. And then launched the windows-node-launcher (from a subfolder inside Bitcoin folder). All good, started slowly and a small popup appeared in systray saying Bitcoin node is syncing. Reviewed the config of Bitcoin and LND through that little app in systray and saw that bitcoin.conf was already filled with some settings. Didn't change anything. After 1 day (with the bitcoin blockchain already synced), the systray popup still says that is syncing and have a red dot. In the tutorial says that we have to leave it to sync until is blue and then green.
I said, ok maybe it has more things to do. So I open that LND Output link, to see what is going on... And I see that LND is not well. Says: 2019-04-06 21:11:29.772 [INF] LTND: Version: 0.6.0-beta commit=v0.6-beta-rc3, build=production, logging=default 2019-04-06 21:11:29.772 [INF] LTND: Active chain: Bitcoin (network=mainnet) 2019-04-06 21:11:29.774 [INF] CHDB: Checking for schema update: latest_version=8, db_version=8 2019-04-06 21:11:29.808 [INF] RPCS: password RPC server listening on 127.0.0.1:10009 2019-04-06 21:11:29.808 [INF] RPCS: password gRPC proxy started at 127.0.0.1:8080 2019-04-06 21:11:29.808 [INF] LTND: Waiting for wallet encryption password. Use lncli create to create a wallet, lncli unlock to unlock an existing wallet, or lncli changepassword to change the password of an existing wallet and unlock it. 2019-04-06 21:11:32.673 [INF] LNWL: Opened wallet 2019-04-06 21:11:33.183 [INF] LTND: Primary chain is set to: bitcoin unable to create chain control: unable to connect to bitcoind: unable to subscribe for zmq block events: dial tcp 127.0.0.1:18502: connectex: No connection could be made because the target machine actively refused it. 2019-04-06 21:11:36.087 [INF] LTND: Shutdown complete unable to connect to bitcoind: unable to subscribe for zmq block events: dial tcp 127.0.0.1:18502: connectex: No connection could be made because the target machine actively refused it. 2019-04-06 21:11:39.229 [INF] LTND: Version: 0.6.0-beta commit=v0.6-beta-rc3, build=production, logging=default
Now the bitcoin.conf have this: printtoconsole=1 rpcallowip=::/0 whitelist=0.0.0.0/0 datadir=C:\Users\Admin\AppData\Roaming\Bitcoin prune=0 txindex=1 server=1 disablewallet=0 timeout=6000 rpcuser=user rpcpassword=defaultxzxxxxx zmqpubrawblock=tcp://127.0.0.1:18502 zmqpubrawtx=tcp://127.0.0.1:18503 dbcache=2408
And LND.conf have this: (#) Auto-Generated Configuration File (#) Node Launcher version 6.0.2 debuglevel=info restlisten=127.0.0.1:8080 rpclisten=127.0.0.1:10009 tlsextraip=127.0.0.1 listen=127.0.0.1:9735 alias=aliasme color=#00aa7f bitcoin.active=1 bitcoin.node=bitcoind bitcoind.rpchost=127.0.0.1:8332 bitcoind.rpcuser=user bitcoind.rpcpass=defaultxxxxx bitcoind.zmqpubrawblock=tcp://127.0.0.1:18502 bitcoind.zmqpubrawtx=tcp://127.0.0.1:18503
So what is going on here? I will have to wait indefinitely? Somebody can give some help or explanation? Is this LND node working on Windows Server 2008 or 2012?
submitted by Mr--Robot to Bitcoin [link] [comments]

Bitcoin Unlimited - "Bitcoin Cash" Ubuntu PPA repo updated to version 1.5.0.1

The Bitcoin Unlimited Ubuntu PPA repository has been updated to serve BUcash version 1.5.0.1 is available at:
https://launchpad.net/~bitcoin-unlimited/+archive/ubuntu/bucash
This release is compatible the Nov 15th 2018 protocol upgrade and propose also a new scheme for miners voting base on BIP 135.
You can configure your BUcash client so that it will activate the protocol upgrade proposed by SV to do so you need to add consensus.forkNov2018Time=0 and consensus.svForkNov2018Time=1 in your bitcoin.conf file.
Trying to activate both protocol upgrades at the same time will lead to the client to exit with this error message: Both the SV and ABC forks are enabled. You must choose one.
See the official announcement for more details:
https://np.reddit.com/btc/comments/9un5jn/bitcoin_unlimited_bitcoin_cash_edition_1501_has/
submitted by s1ckpig to btc [link] [comments]

DAG Technology Analysis and Measurement

The report produced by the fire block chain coins Institute, author: Yuan Yuming, Hu Zhiwei, PDF version please read the original text download
Summary
The Fire Coin Blockchain Application Research Institute conducts research on distributed ledger technology based on directed acyclic graph (DAG) data structure from a technical perspective, and through the specific technical test of typical representative project IOTA, the main research results are obtained:
Report body
1 Introduction
Blockchain is a distributed ledger technology, and distributed ledger technology is not limited to the "blockchain" technology. In the wave of digital economic development, more distributed ledger technology is being explored and applied in order to improve the original technology and meet more practical business application scenarios. Directed Acylic Graph (hereinafter referred to as "DAG") is one of the representatives.
What is DAG technology and the design behind it? What is the actual application effect?We attempted to obtain analytical conclusions through deep analysis of DAG technology and actual test runs of representative project IOTA.
It should also be noted that the results of the indicator data obtained from the test are not and should not be considered as proof or confirmation of the final effect of the IOTA platform or project. Hereby declare.
2. Main conclusions
After research and test analysis, we have the following main conclusions and technical recommendations:
3.DAG Introduction
3.1. Introduction to DAG Principle
DAG (Directed Acyclic Graph) is a data structure that represents a directed graph, and in this graph, it cannot return to this point (no loop) from any vertex, as shown in the figure. Shown as follows:
📷
After the DAG technology-based distributed ledger (hereinafter referred to as DAG) technology has been proposed in recent years, many people think that it is hopeful to replace the blockchain technology in the narrow sense. Because the goal of DAG at design time is to preserve the advantages of the blockchain and to improve the shortcomings of the blockchain.
Different from the traditional linear blockchain structure, the transaction record of the distributed ledger platform represented by IOTA forms a relational structure with a directed acyclic graph, as shown in the following figure.
📷
3.2. DAG characteristics
Due to the different data structure from the previous blockchain, the DAG-based distributed ledger technology has the characteristics of high scalability, high concurrency and is suitable for IoT scenarios.
3.2.1. High scalability, high concurrency
The data synchronization mechanism of traditional linear blockchains (such as Ethereum) is synchronous, which may cause network congestion. The DAG network adopts an asynchronous communication mechanism, allowing concurrent writing. Multiple nodes can simultaneously trade at different tempos without having a clear sequence. Therefore, the data of the network may be inconsistent at the same time, but it will eventually be synchronized.

3.2.2. Applicable to IoT scenarios

In the traditional blockchain network, there are many transactions in each block. The miners are packaged and sent uniformly, involving multiple users. In the DAG network, there is no concept of “block”, the smallest unit of the network. It is a "transaction", each new transaction needs to verify the first two transactions, so the DAG network does not need miners to pass the trust, transfer does not require a fee, which makes DAG technology suitable for small payments.
4. Analysis of technical ideas
Trilemma, or "trilemma", means that in a particular situation, only two of the three advantageous options can be selected or one of the three adverse choices must be chosen. This type of selection dilemma has related cases in various fields such as religion, law, philosophy, economics, and business management.Blockchain is no exception. The impossible triangle in the blockchain is: Scalability, Decentralization, and Security can only choose two of them.
If you analyze DAG technology according to this idea, according to the previous introduction, then DAG has undoubtedly occupied the two aspects of decentralization and scalability. The decentralization and scalability of the DAG can be considered as two-sided, because of the asynchronous accounting features brought about by the DAG data structure, while achieving the high degree of decentralization of the participating network nodes and the scalability of the transaction.
5. There is a problem
Since the characteristics of the data structure bring decentralization and scalability at the same time, it is speculated that the security is a hidden danger according to the theory of impossible triangles. But because DAG is a relatively innovative and special structure, can it be more perfect to achieve security? This is not the case from the actual results.
5.1. Double flower problem
The characteristics of DAG asynchronous communication make it possible for a double-flower attack. For example, an attacker adds two conflicting transactions (double spending) at two different locations on the network, and the transactions are continuously forward-checked in the network until they appear on the verification path of the same transaction, and the network discovers the conflict. At this time, the common ancestor nodes that the two transactions are gathered together can determine which transaction is a double-flower attack.
If the trading path is too short, there will be a problem like "Blowball": when most transactions are "lazy" in extreme cases, only the early trading, the trading network will form a minority. Early transactions are the core central topology. This is not a good thing for DAGs that rely on ever-increasing transactions to increase network reliability.
Therefore, at present, for the double flower problem, it is necessary to comprehensively consider the actual situation for design. Different DAG networks have their own solutions.
5.2. Shadow chain problem
Due to the potential problem of double flowers, when an attacker can build a sufficient number of transactions, it is possible to fork a fraudulent branch (shadow chain) from the real network data, which contains a double flower transaction, and then this The branch is merged into the DAG network, and in this case it is possible for this branch to replace the original transaction data.
6. Introduction to the current improvement plan
At present, the project mainly guarantees safety by sacrificing the native characteristics of some DAGs.
The IOTA project uses the Markov chain Monte Carlo (MCMC) approach to solve this problem. The IOTA introduces the concept of Cumulative Weight for transactions to record the number of times the transaction has been cited in order to indicate the importance of its transaction. The MCMC algorithm selects the existing transactions in the current network as a reference for the newly added transactions by weighting the random weights of the accumulated weights. That is, the more referenced the transaction path, the easier it is to be selected by the algorithm. The walk strategy has also been optimized in version 1.5.0 to control the "width" of the transaction topology to a reasonable range, making the network more secure.
However, at the beginning of the platform startup, due to the limited number of participating nodes and transactions, it is difficult to prevent a malicious organization from sending a large number of malicious transactions through a large number of nodes to cause the entire network to be attacked by the shadow chain. Therefore, an authoritative arbitration institution is needed to determine the validity of the transaction. In IOTA, this node is a Coordinator, which periodically snapshots the current transaction data network (Tangle); the transactions contained in the snapshot are confirmed as valid transactions. But Coordinator doesn't always exist. As the entire network runs and grows, IOTA will cancel the Coordinator at some point in the future.
The Byteball improvement program features its design for the witness and the main chain. Because the structure of DAG brings a lot of transactions with partial order, and to avoid double flowers, it is necessary to establish a full order relationship for these transactions to form a transaction backbone. An earlier transaction on the main chain is considered a valid transaction.Witnesses, who are held by well-known users or institutions, form a main chain by constantly sending transactions to confirm other user transactions.
The above scheme may also bring different changes to the platform based on the DAG structure. Taking IOTA as an example, because of the introduction of Coordinator, the decentralization characteristics are reduced to some extent.
7. Actual operation
7.1. Positive effects
In addition to solving security problems, the above solutions can also solve the smart contract problem to some extent.
Due to the two potential problems caused by the native features of DAG: (1) The transaction duration is uncontrollable. The current mechanism for requesting retransmission requires some complicated timeout mechanism design on the client side, hoping for a simple one-time confirmation mechanism. (2) There is no global sorting mechanism, which results in limited types of operations supported by the system. Therefore, on the distributed ledger platform based on DAG technology, it is difficult to implement Turing's complete intelligent contract system.
In order to ensure that the smart contract can run, an organization is needed to do the above work. The current Coordinator or main chain can achieve similar results.
7.2. Negative effects
As one of the most intuitive indicators, DAG's TPS should theoretically be unlimited. If the maximum TPS of the IOTA platform is compared to the capacity of a factory, then the daily operation of TPS is the daily production of the plant.
For the largest TPS, the April 2017 IOTA stress test showed that the network had transaction processing capabilities of 112 CTPS and 895 TPS. This is the result of a small test network consisting of 250 nodes.
For the daily operation of TPS, from the data that is currently publicly available, the average TPS of the main network in the near future is about 8.2, and the CTPS (the number of confirmed transactions per second) is about 2.7.
📷
The average average TPS of the test network is about 4, and the CTPS is about 3.
📷
Data source discord bot: generic-iota-bot#5760
Is this related to the existence of Coordinator? Actual testing is needed to further demonstrate.
8. Measured analysis
The operational statistics of the open test network are related to many factors.For further analysis, we continue to use the IOTA platform as an example to build a private test environment for technical measurement analysis.
8.1. Test Architecture
The relationship between the components we built this test is shown below.
📷
among them:
8.2. Testing the hardware environment
The server uses Amazon AWS EC2 C5.4xlarge: 16 core 3GHz, Intel Xeon Platinum 8124M CPU, 32GB memory, 10Gbps LAN network between servers, communication delay (ping) is less than 1ms, operating system is Ubuntu 16.04.
8.3. Test scenarios and results analysis

8.3.1. Default PoW Difficulty Value

Although there is no concept such as “miners”, the IOTA node still needs to prove the workload before sending the transaction to avoid sending a large number of transactions to flood the network. The Minimum Weight Magnitude is similar to Bitcoin. The result of PoW should be the number of digits of "9", 9 of which is "000" in the ternary used by IOTA. The IOTA difficulty value can be set before the node is started.
Currently for the production network, the difficulty value of the IOTA is set to 14; the test network is set to 9. Therefore, we first use the test network's default difficulty value of 9 to test, get the following test results.
📷
Since each IOTA's bundle contains multiple transfers, the actual processed TPS will be higher than the send rate. But by executing the script that parses zmq, it can be observed that the current TPS is very low. Another phenomenon is that the number of requests that can be sent successfully per second is also low.
After analysis, the reason is that the test uses VPS, so in PoW, the CPU is mainly used for calculation, so the transaction speed is mainly affected by the transmission speed.

8.3.2. Decrease the PoW difficulty value

Re-test the difficulty value to 1 and get the following results.
📷
As can be seen from the results, TPS will increase after the difficulty is reduced. Therefore, the current TPS of the IOTA project does not reach the bottleneck where the Coordinator is located, but mainly because of the hardware and network of the client itself that sends the transaction. The IOTA community is currently working on the implementation of FPGA-based Curl algorithm and CPU instruction set optimization. Our test results also confirm that we can continue to explore the performance potential of the DAG platform in this way.

8.3.3. Reduce the number of test network nodes

Due to the characteristics of DAG, the actual TPS of the platform and the number of network nodes may also be related. Therefore, when the difficulty value is kept at 1, the number of network nodes is reduced to 10 and the test is repeated to obtain the following results.
📷
As can be seen from the results, as the number of nodes decreases, the actual processing of TPS also decreases, and is lower than the transmission rate. This shows that in a DAG environment, maintaining a sufficient size node will facilitate the processing of the transaction.
9. Reference materials
Https://www.iota.org/
https://en.wikipedia.org/wiki/Trilemma
Https://blog.iota.org/new-tip-selection-algorithm-in-iri-1-5-0-61294c1df6f1
https://en.wikipedia.org/wiki/Markov\_chain\_Monte\_Carlo
Https://byteball.org/
Https://www.iotachina.com/iota.html
Https://www.iotachina.com/iota\_tutorial\_1.html
submitted by i0tal0ver to Iota [link] [comments]

How to install Bitcoin Armory in Ubuntu 14.04 Bitcoin Client Update 0.10.0rc1 [Unstable] Compile Bitcoin's source code (0.13) 4. Installing Bitcoin Core on Linux How to Install Bitcoin Core Wallet on Ubuntu 16

How do I update ubuntu packages 16.04 with Terminal? 2. What does the command “sudo apt-get install upgrade-system” do? 0. Trying to make sure my system is updated properly. Ubuntu20.04 . 0. I need help fixing my screen resolution. 0. E: Unable to locate package update. 0. How to update to a specific version of Ubuntu? 1. Can't update, can't install from SC 18.04. 0. Question about ... Bitcoin has now an officially maintained PPA with a release candidate version of the peer-to-peer daemon and the client.. Bitcoin has a launchpad project i.e. same project status as Unity/Docky/Openshot etc. The maintainer - Matt Corallo - is a major contributor to the official bitcoin.org website.. This will upgrade all versions from 10.04 and later. Next, update Ubuntu’s software package lists: $ sudo apt-get update Finally, install Bitcoin core itself. Enter “Y” when asked asked for permission to continue: $ sudo apt-get install bitcoin-qt This last command may take some time, during which both Bitcoin Core and all of its dependencies will be installed. Run Bitcoin Core Luckily for Ubuntu users, well tested DEB packages are available for easy installation of Armory Bitcoin client. Installation of Armory in Ubuntu is rather simple. Download the appropriate DEB file. And double-click to install it. Ubuntu Software Center will do the rest. Before installing though, I would recommend you to verify the authenticity of the downloaded Armory DEB package by following ... Download Ubuntu desktop, Ubuntu Server, Ubuntu for Raspberry Pi and IoT devices, Ubuntu Core and all the Ubuntu flavours. Ubuntu is an open-source software platform that runs everywhere from the PC to the server and the cloud.

[index] [19070] [17653] [40799] [8274] [10410] [7312] [12978] [48098] [5645] [47334]

How to install Bitcoin Armory in Ubuntu 14.04

Bitcoin Core is the open source client of the bitcoin cryptocurrency. Initially, the software was published by Satoshi Nakamoto under the name Bitcoin, then Bitcoin-Qt and later renamed to Bitcoin ... This short video shows how to compile the bitcoin source code on linux (ubunu). an easy task to do but it take some time (around 15 min) please read the instruction in the official github https ... sudo add-apt-repository ppa:bitcoin/bitcoin sudo apt-get update sudo apt-get install bitcoin-qt bitcoind Linux terminal new stuff: clear, ll, cd, touch, echo, cat, shutdown www.bitcoinhackers.org How to Install Ubuntu and Optimize CGMiner for Litecoin Mining Rig! - Duration: 48:56. ... Easy Bitcoin Electrum Wallet/Client tutorial for beginners. 2014. - Duration: 14:10. Dash Infonode 68,293 ... Cryptocoin Wallet Backup/Restore Ubuntu(Linux) CryptoCoin Videos . Loading... Unsubscribe from CryptoCoin Videos? Cancel Unsubscribe. Working... Subscribe Subscribed Unsubscribe 14. Loading ...

#