bitcoin-testnet-box/Dockerfile at master · freewil/bitcoin ...


Aeon (AEON) is a private, secure, untraceable currency. You are your bank, you control your funds, and nobody can trace your transfers.

Setting up a Lightning Network Node on Testnet using Ubuntu, Bitcoin Core and C-Lightning /r/Bitcoin

Setting up a Lightning Network Node on Testnet using Ubuntu, Bitcoin Core and C-Lightning /Bitcoin submitted by BitcoinAllBot to BitcoinAll [link] [comments]

Gridcoin "Fern" Release
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.



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.


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.


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



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.







As a reminder:









Detailed Changelog

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





submitted by jamescowens to gridcoin [link] [comments]

Question about LND

I compiled LND from source on Ubuntu 18 and have a full (non-pruned) indexed bitcoind node on the same machine. The setup instructions say to use
lnd --bitcoin.testnet --debuglevel=debug --bitcoin.node=bitcoind --bitcoind.rpcuser=xxxx --bitcoind.rpcpass=xxxx --bitcoind.zmqpubrawblock=tcp:// --bitcoind.zmqpubrawtx=tcp:// --externalip=xxxx 
However, I didn't use --bitcoin.testnet. I used --bitcoin.mainnet instead. Is that ok? Are there any drawbacks to this? I can confirm that the wallet was created in ~/.lnd/data/chain/bitcoin/mainnet/ Also, my bitcoin.conf file has testnet=0. I haven't done anything else yet.
submitted by 1Tim1_15 to lightningnetwork [link] [comments]

Electrum wont connect to mynode

having some issues with Electrum wallet on Ubuntu 20.04 LTS. i got it to install properly with no issues. but it seems like i am now have trouble connecting it to my node, below is what my .desktop file looks like
# If you want Electrum to appear in a Linux app launcher ("start menu"), install this by doing:
# sudo desktop-file-install electrum.desktop

[Desktop Entry]
Comment=Lightweight Bitcoin Client
Exec=sh -c "PATH=\"\\$HOME/.local/bin:\\$PATH\"; electrum --oneserver --server localhost:50001:t %u"
GenericName[en_US]=Bitcoin Wallet
GenericName=Bitcoin Wallet
Name[en_US]=Electrum Bitcoin Wallet
Name=Electrum Bitcoin Wallet

[Desktop Action Testnet]
Exec=sh -c "PATH=\"\\$HOME/.local/bin:\\$PATH\"; electrum --testnet %u"
Name=Testnet mode

when opening up the wallet, i get the red dot on the bottom right hand corner, i can ping and access mynode via the local 192. address and i see electrum server is running. does it matter where the electrum.desktop file is located? as of right now i have it under /home/gp11/Downloads. is there anything else i can check? even if i remove electrum --oneserver --server localhost:50001:t i still get the same result with no connection, where i am thinking if i remove the line of code it should connect to other nodes.
currently using myNode community Version 0.2.09 any help here would be appreciated - thanks in advance.
submitted by lifeofgp to Electrum [link] [comments]

Groestlcoin 6th Anniversary Release


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?

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.
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.

Other Linux


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


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.





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.



Main Release (Main Net)
Testnet Release


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.


Live Version (Not Recommended)



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).





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).




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.


Remastered Improvements



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.



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


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.



Linux / OSX (Instructions)


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.



Main Net
Main Net (FDroid)
Test Net


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.




UPDATED – P2Pool Test Net



Pre-Hosted Testnet P2Pool is available via


submitted by Yokomoko_Saleen to groestlcoin [link] [comments]

I'm too late.

I'm too late to be an early adopter of BTC, I screwed around in my CompSci classes a decade before the Genesis block instead of helping. I'm too late to mine BTC on my CPU, by almost a decade. I'm too late to mine BTC on my GPU, by several years. I'm almost too late to mine BTC on my ASICs, they'll be out of date in a few years. Maybe less. I've made TWO purchases with BTC, both to buy another ASIC. I'm sold some BTC. Ok, I'm too early there, but regret it just the same.
I just spun up a testnet BTC node and installed the Eclair Lightning Network client.
I did it on an OS I'm really not familiar with, Ubuntu is just different enough from Win10 to make me struggle. I could have done it on Win10, I chose the harder route.
I'm NOT too late to do my little part to make this happen. I opened a channel between a testnet Core wallet and an online testnet wallet and bounced Lightning transactions back and forth for an hour, taking only a few seconds between transactions. Paid only 2 miner's fees.
I could have sent transactions to anyone running a connected Lightning client just as fast. And vice versa. It took half an hour to fund the channel, yes. And another half an hour or so to secure my funds when I closed the channel. Had I done those transactions without Lightning, it'd have taken most of a day. Not even Bitcoin Cash's large block size could have done that, its limited by the same 10 minute heartbeat Bitcoin has.
THIS feels like the future. I am NOT too late. Noone is.
Edit: Holy moly my inbox. Thank you for the Gold, now I have something more to research. :) I did NOT expect this post to get that many hits overnight! It took me a while to read thru the comments, every one of them to this point, and I'm glad to see so much agreement, discussion, arguments, and even veiled insults to my username. Its all good, I get far worse on a good day IRL. A few more people know about LN, some good explanations were given, that is the kind of thing we're going to need to bootstrap the LN network. The complexity is a problem compared to standard bitcoin transactions and wallets...but you realize just how complex those wallets and transactions are? Maybe not, well-designed software hides all the gorey details. I imagine LN wallets will be the same given more development, all the channel business hidden to anyone using Easy-mode and the refunding of channels handled behind the scenes.
Probably not the best place to put something like this, in an edit, but oh well. Again, thank you everyone, I'm gonna go do something not-BTC related for a few hours now, have fun!
submitted by NDragon951 to Bitcoin [link] [comments]

Bitcoin Unlimited - Bitcoin Cash edition has just been released

Download the latest Bitcoin Cash compatible release of Bitcoin Unlimited (, August 17th, 2018) from:
This release is a major release which is compatible with the Bitcoin Cash compatible with the Bitcoin Cash specifications you could find here:
A subsequent release containing the implementation of the November 2018 specification will be released soon after this one.
List of notable changes and fixes to the code base:
Release notes:
Ubuntu PPA repository for BUcash has been updated
submitted by s1ckpig to btc [link] [comments]

An Idiots (me) Guide To Installing A Citizen Node.

An Idiots (me) Guide To Installing A Citizen Node.
So I dusted off an old laptop and have compiled a how-to install the Iconloop Engine and Iconservice on Linux and OSX. The directions on github are very good but there are a few issues with OSX and Xcode. Here is my simple how to with work arounds for Xcode on OSX and simple compiling for OSX. I will edit this as need be and it isn't exhaustive but rather a good solid how-to for anyone that wants to play around with our favorite open source project. Some of the packages for Ubuntu took a little searching and I hope this saves somebody some time.
Have a great day.
Install make tools, rabbitmq-server, opensssl, pkg-config
$ sudo apt install automake pkg-config libtool rabbitmq-server openssl
Install libsec256k1-0 $ sudo apt-get install libsecp256k1-0
$ sudo apt-get install python3 $ sudo apt-get install python3-distuttils $ sudo apt-get install python3-set-proctitle $ sudo apt-get install python3-devel
LevelDB: Linux
$ sudo apt-get install libsnappy-dev
$ export VER="1.20"
$ wget
$ tar xvf v1.20.tar.gz
$ rm -f v$1.20.tar.gz
$ cd leveldb-$1.20
$ make
$ sudo scp -r out-static/lib* out-shared/lib* "/uslocal/lib"
$ cd include
$ sudo scp -r leveldb /uslocal/include
$ sudo ldconfig
Loopchain Engine:
Download zip: Unzip
$ cd /home/useDownloads $ ls-la $ cd /loopchain-master install libtolls-bin otherwise make won't work. $ sudo apt install libtool-bin $ service rabbitmq-service start $ source venv/bin/activate $ (venv)$ ./ $ make setup $ make install $ loop citizen -r testnet
Apply passcode when prompted
Iconloop engine now running.
$ virtualenv -p python3 venv
Setting up Icon Service # Create a working directory $ mkdir work $ cd work
# Setup the python virtualenv development environment $ virtualenv -p python3 venv $ source venv/bin/activate
# Install the ICON SCORE dev tools (venv) $ pip install iconservice
Xcode: You'll need Xcode 9.4 from Apple Developer, lstdc++ is deprecated. Manually link library from Xcode 9.4
cp /Applications/* /Applications/
For Simulator :
cp /Applications/* /Applications/
Install Homebrew
Manually install bitcoin-core/secp256k1
cd /path/to/download
$ ./ $ ./configure $ make $ ./tests $ sudo make install
For OSX follow the directions at the project after you have shared Xcode libraries from 9.4 to the current Xcode per the instructions above.
Any feedback most helpful.
submitted by 1_2_123 to helloicon [link] [comments]

Vertnode - An automated solution for installing Vertcoin node(s) on Single Board Computers

Hello Vertcoin Community,
Eager to contribute to the Vertcoin Community I began creating step by step walkthrough guides on how to get a Vertcoin node up and running on a Raspberry Pi, Raspberry Pi Zero and Intel NUC. Along with information to get a Vertcoin node up and running was also optional steps to install p2pool-vtc.
I decided that while this step by step guide might be helpful to a few, a setup script may prove to be useful to a wider range of people. I have this script to a point where I think it may be productive to share with a bigger audience, for those who are brave and have this hardware sitting around or like to tinker with projects; I invite you to test this setup script if you are interested, if you run into errors any sort of verbose console output of the error proves to be extremely helpful in troubleshooting.
The script was designed to produce a “headless” server... meaning we will not be using a GUI to configure Vertcoin or check to see how things are running. In fact, once the server is set up, you will only interact with it using command line calls over SSH. The idea is to have this full node be simple, low-power, with optimized memory usage and something that “just runs” in your basement, closet, etc.
Why run a headless node on a Single Board Computer?
The idea is to have this full node be simple, low-power, with optimized memory usage and something that “just runs” in your basement, closet, etc.
Required: USB Flash Drive 6GB - 32GB
Please note that the script was designed for Single Board Computers first and looks for an accessible USB Flash Drive to use for storing the blockchain and swap file, as constant writing to a microSD can degrade the health of the microSD.


All of the hardware listed above is hardware that I have personally tested / am testing on myself. The plan is to continue expanding my arsenal of single board computers and continue to add support for more hardware to ensure as much compatibility as possible.
It is worth noting that LIT can be ran with multiple configurations, the ones displayed in the Post Installation Report reflect values that run LIT with the Vertcoin Mainnet. Please be aware that the Vertcoin Testnet chain has not been mined 100% of the time in the past, if you make transactions on the Vertcoin testnet that do not go through it is likely because the chain has stopped being mined.

Vertcoin Testnet Coins
I've included some documentation on LIT I created which includes information I found to be useful:
Please visit the mit-dci/lit github repository for the most up to date information on lit:

Vertnode | Automated Vertcoin Node Installation Script

Recommended: Use Etcher to install the chosen OS to your microSD card / USB flash drive.

If you intend on installing Ubuntu Server 16.04 to your Intel NUC please use Etcher to install the .iso to your USB flash drive.

Ubuntu Server 16.04 Setup Details

You can use different clients to ssh into your node. One option is using PuTTY or Git Bash on Windows which is included in the desktop version of Git. If you are using Linux you can simply open a new terminal window and ssh to the IP address of your node (hardware you intend installing the Vertcoin node on).
You will need to know the IP address of your node, this can be found on your router page.
ssh -l pi For example, this command uses ssh to login to using the -l login name of pi. The IP address of your node will likely be different for you, in this example I am logging into a Raspberry Pi which has a default login name of pi.
A brief list of commands that can be used to check on the Vertcoin node status:
vertcoin-cli getblockchaininfo | Grab information about your blockchain
vertcoin-cli getblockcount | Grab the current count of blocks on your node
vertcoin-cli getconnectioncount | Grab the current count of connections to your node. A number of connections larger than 8 means that you have incoming connections to your node. The default settings are to make 8 outgoing connections. If you want incoming connections please port forward your Raspberry Pi in your Router settings page.
vertcoin-cli getpeerinfo | Grab the information about the peers you have connected to / are connected to
vertcoin-cli getnettotals | Grab network data, how much downloaded/upload displayed in bytes
tail -f ~/.vertcoin/debug.log | Output the latest lines in the Vertcoin debug.log to see verbose information about the Vertcoin daemon (ctrl+c to stop)
Thank you to all who have helped me and inspired me thus far, @b17z, @jamesl22, @vertcoinmarketingteam, @canen, @flakfired, @etang600, @BDF, @tucker178, @Xer0
This work is dedicated to the users of Vertcoin, thank you for making this possible.
7/20/2018 Thank you @CommodoreAmiga for the incredibly generous tip <3
You can reach me @Sam Sepiol#3396 on the Vertcoin Discord, here on reddit or @ [email protected]
submitted by ecorp-sam-sepiol to vertcoin [link] [comments]

Ren | All-In-One


What is Ren? Ren is an open protocol that enables the permissionless transfer of value between any blockchain. Ren's core product, RenVM, brings interoperability to decentralized finance (DeFi).
What makes RenVM unique is that it does everything in secret using zero-knowledge proofs over an sMPC based protocol that the team has pioneered. The state, inputs, and outputs of all programs that RenVM runs are kept hidden from everyone, including the Darknodes that power it.
This allows RenVM to securely manage (ECDSA) private keys on different blockchains, making it possible to shift tokens between these blockchains in a trustless, permissionless, and decentralized way (i.e interoperability).
Technically speaking RenVM is a byzantine fault-tolerant protocol (with 1/3 malicious nodes) that does ECDSA threshold key generation and signing via sMPC. RenVM is not a product or an application in and of itself but is a network (and an accompanying SDK) that allows developers to bring interoperability to their DeFi applications.
Ren was founded in 2017 and is headquartered in Singapore.

RenVM Mainnet Is Live! 🎉

RenBridge (dapp)| Mint BTC, BCH, and ZEC on Ethereum

Official Resources
Darknodes are the physical machines that power RenVM, where every machine contributes CPU time for compute power and its disk space for storage. These are that machines that form the P2P decentralized network (not a blockchain) that cooperate to run secret multiparty computations. It is important to note that programs executing on RenVM are hidden from the Darknodes that run the virtual machine.
This guide will walk you through the installation of your Darknode. Before you begin, make sure that you have a MacOS, Windows, or Ubuntu machine available (i.e. home computer) and 100,000 REN.
Guides: How to set up a Darknode
The Team
Ren Linkedin Page
General Updates | Blog
2020 Development & Ecosystem Updates
Podcasts & Youtube videos | Chronological Order
REN Exchanges
REN Token Details
What happened to the Republic Protocol?
Republic Protocol was rebranded to Ren to reflect the project’s evolution towards interoperability (i.e. RenVM). Old posts and discussions can be found on the Republic Protocol Reddit

Closing Thoughts

We truly appreciate our community, and this cannot be said enough. The level of technical understanding and subsequent assistance provided to our newcomers, speaks to the expertise and positivity in the community, and we couldn’t be more thankful.
We look forward to collaborating with everyone as we make our next steps forward towards building a cross-chain DeFi ecosystem. If you are interested in working directly with the Ren Team we are always looking for developers so please do reach out via the below email.
Need help or want to partner? [[email protected]](mailto:[email protected])
submitted by RENProtocol to RenProject [link] [comments]

List of Lightning Network wallets, node guides for different OS, payments processors

credits to u/bitusher who initially posted this list here.
Keep in mind that this list likely will be incomplete a few weeks from now on, as new wallets (like LND wallet, ZAP, Shango etc) are in the late development phases and will come online "soon", as well as new merchants, new guides etc.
LN on IOS – LND Thin Wallet: (You need to connect to your own LN node)
LN on Android:
Bitcoin Lightning Wallet:
Eclair (pay or send only for android for LN / send and receive all btc onchain txs)
Eclair youtube tutorial 1
Eclair youtube tutorial 2
LN on Linux or Ubuntu: (or with windows in virtualbox)
LN on VPS:
LN on raspberry-pi:
LN on Windows:
LN on OSX:
LN on Google cloud:
Hosted Lightning payment processors: (Free LN payment processor)
LN megathread:
Stores that accept Lightning payments:
accept LN for free with:
Ultimate guide to setting up BTCpay:
videos as well:
submitted by TheGreatMuffin to Bitcoin [link] [comments]

A response to the GRS Shill cries

First of all, I think it is right to say that it wouldn’t be fair for the recent reddit to be entirely attributed to the recent 130% rise in GRS price – The price has gone a lot higher when SegWit was activated and a lot higher in the runup to the previous release announcement (22nd September) and was arguably at the ‘floor’ when it was discovered by us.
I’d like to give a little bit of a backstory on the recent discovery of GRS by a small group of people in a hope you realise this isn’t just shilling some shit-coin for a pump and dump. It was never our intention to come across as shilling and certainly not our intention to attract ‘pump and dump’ groups. We merely searched for SegWit-activated coins, and the main one that kept popping up was Groestlcoin, in posts that didn’t even mention Litecoin or Vertcoin. We thought that it was worth investigating further and decided to do some more research, and the more we found we more we realised that this was a genuine diamond amongst the rocks. 254th in market cap, first to activate SegWit, Lightning Network in full development, the list was endless – and seemingly nobody knew about it which was insanity.
In several places we saw that no marketing was done or being actively planned, and it was up to the community to market the coin if they wanted to whilst the 20+ developers keep cracking on to try and be the first to more developments.
We contacted the lead developer, ‘Jackielove4u’ and started a plan to try and market the coin, first by creating a Discord channel for discussions and then by trying to get their great features out to the world and aim for slow-and-steady growth.
In hindsight, a bit more finesse would have been better and the reddit posts got a little out-of-hand, if I didn’t know any better I would have seen GRS as a coin being shilled too on Reddit, and I have accused people of doing the same with Vertcoin in the past. So I thought I’d try to clear up some misconceptions and give one targeted response post to the cries of shilling and try to give the facts to the best of my knowledge, whilst trying to give an unbias opinion as much as I can based on my views and the views of the response that we’ve had.
• Segwit Enabled Enabled first)
• Low-Power Mining – This is a selling point but people have said the power consumption is on-par with Vertcoin. I think the mining uses 2 rounds of Groestl algorithm hashing to make it more secure but is still very low on power consumption and hardware wear
• Lightning Network currently in development
• They have had an easy miner solution since 2015 – Although I’d be the first to admit it is a little clunky, but is openly on Git for improvements.
• 3 iOS wallets (Including a shared wallet), 11 android wallets (1x Secure BIP147, 1x Including sending GRS via SMS, 1x ability to use NFC tags as encryption keys), 11 blackberry wallets (Secure), 3 web wallets and 10 desktop wallets with varying features / designs – More to come on the differences soon.
• Over 80 electrum servers
• Working testnet
• Hosts their own block explorer
• Officially maintained by the Bitcoin Debian packaging team
• Ubuntu PPA available
• ASIC resistant, profitable CPU and GPU mining (And has an ARM miner apparently!) We’re just brushing the surface of the great tech that is being developed by the GRS developers.
• Elephant in the room – The name. People have called it ugly, most don’t know how to pronounce it (It’s Groosel-coin). The developers are open to a rebrand pending a community vote in 2018.
• I’ve heard a few times ‘that logo looks like a cross between google and wordpress’. Again the logo is open to rebrand/redesign pending a vote (open for suggestions/examples!) but there is some significance in it. The ‘2’ in the logo is for the 2 rounds of Groestl algorithm hashing that is used.
• Obviously little or no marketing up until this point. Marketing is important (if not vital) for the success of a coin so we’re trying to spread some awareness.
• Lots of internet posts saying that it is a scam coin. From what I can see it seems to be because the coin has been ‘pumped-and-dumped’ a few times? By that logic, most coins are scam coins? The block reward dropped 6% a week when it was first launched specifically to prevent pump-and-dumps.
• Rumours of a pre-mine of 0.2% (240,000 coins) when it was first created. I haven’t gotten to the bottom of this to confirm or deny, but if it was true it seems to have been given as rewards for some early marketing (where those odd naked women pictures come from) and some early bounty rewards to get the ball rolling. No pre-mine is ideal but its personally something I can look over now if it IS true.
• Over 70% of the mined coins are owned by the top 100 addresses. Again, this is clearly an issue that many other coins also are facing (albeit some to a lesser extent). I can only guess that the more time that passes being a lesser-known coin, the greater risk that this becomes as the same miners mine for a longer period of time. Not sure if this matters much but it’s also worth noting that 24% of the mined coins appear to be on Bittrex currently.
TL:DR – Trying not to shill GRS, just trying to get the word out. Criticisms about the coin have been noted by the developers and they are very open to change and improvements suggested if they are the popular vote. I recommend that you research more into the coin, coin the discord on and make a decision based on your own research whether you'd see something in, and like to support the coin.
Apologies for such a long post..
submitted by Yokomoko_Saleen to groestlcoin [link] [comments]

Interesting technical facts about Groestlcoin that might explain price rise

Disclaimer: After doing some research, I own a small amount of Groestlcoin and no Vertcoin (I rkn VTC is overvalued currently). Might buy some VTC after it corrects. Here's why...
Original text: Posted by posted [–]jackielove4u 4 days ago
Our selling points are:
submitted by enozym111 to CryptoCurrency [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
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
submitted by i0tal0ver to Iota [link] [comments]

Bitcoin Core & Lightning Network (very easy installation!) No root access!

I finished the fine tools as i think
I created Makefile utilities for bitcoind & lnd compilation under $HOME directory (no root access!)
This makefile does everything for full bitcoin node and lightning network node. This kit was created for CentOS 6.* but it works in Ubuntu / Linux Mint OSes too and may be will work in 90% Unix systems.
It compiles from sources under $HOME directory: compilers (gcc 7.1, go, node.js, python2 & python3) and tools (autoconf & autotools and etc), all libraries (boost, openssl and more), bitcoind daemon, lnd daemon , lncli-web client (and node.js for this) and does all configuration for you! You need only create a wallet in lnd. It works fine with UPnP routers (from sources too!) and can define network configuration (real public IP & network interfaces)
So if you want to have bitcoind & lnd node you need only to do:
make i-want-lightning
make set-up-lightning-mainnet
And after you can run:
And after you will have bitcoind full node & lnd node with web interface (lncli-web)
You can setup in one host mainnet & testnet daemons without any conflicts.
submitted by Perlover to Bitcoin [link] [comments]

Why is does it take so long to shut down an node used only as a JSON-RPC server?

I'm trying to sync a full node that will only be used as a JSON-RPC server (no mining). I tried to modify the config file and added a service unit, so that the node can run in a low-end VPS with minimum RAM and CPU capabilities. The problem is that the server takes too long to stop, and it's terminated by the system, so it always start rewinding blocks that have been already downloaded.
Here is my configuration file:
server=1 daemon=1 #debug=mempool debug=rpc # If run on the test network instead of the real bitcoin network # testnet=1 # You must set rpcuser and rpcpassword to secure the JSON-RPC api # Please make rpcpassword to something secure, `5gKAgrJv8CQr2CGUhjVbBFLSj29HnE6YGXvfykHJzS3k` for example. # Listen for JSON-RPC connections on  (default: 8332 or testnet: 18332) rpcuser=myuser rpcpassword=pypassword rpcport=8332 # Enable blocks pruning #prune=550 # Limit dbcache=50 maxconnections=4 rpcthreads=2 
And the service unit:
# It is not recommended to modify this file in-place, because it will # be overwritten during package upgrades. If you want to add further # options or overwrite existing ones then use # $ systemctl edit bitcoind.service # See "man systemd.service" for details. # Note that almost all daemon options could be specified in # /etc/bitcoin/bitcoin.conf [Unit] Description=Bitcoin daemon [Service] ExecStart=/usbin/bitcoind -daemon=0 -datadir=/home/jsonrpc/bitcoin -conf=/home/jsonrpc/bitcoin/settings.conf ExecStop=/usbin/bitcoin-cli -datadir=/home/jsonrpc/bitcoin -conf=/home/jsonrpc/bitcoin/settings.conf stop # Creates /run/bitcoind owned by bitcoin #RuntimeDirectory=/home/jsonrpc/bitcoin WorkingDirectory=/home/jsonrpc/bitcoin User=jsonrpc Group=jsonrpc TimeoutStopSec=15m #CPUQuota=4% #MemoryLimit=128M #IOReadIOPSMax=10 #IOWriteIOPSMax=10 Type=simple #Restart=on-failure # Hardening measures #################### # Provide a private /tmp and /vatmp. PrivateTmp=true # Mount /usr, /boot/ and /etc read-only for the process. ProtectSystem=full # Disallow the process and all of its children to gain # new privileges through execve(). NoNewPrivileges=true # Use a new /dev namespace only populated with API pseudo devices # such as /dev/null, /dev/zero and /dev/random. PrivateDevices=true # Deny the creation of writable and executable memory mappings. # Commented out as it's not supported on Debian 8 or Ubuntu 16.04 LTS #MemoryDenyWriteExecute=true [Install] 
submitted by rraallvv to Bitcoin [link] [comments]

IRC Log from Ravencoin Open Developer Meeting - Aug 10, 2018

[16:01] <@Wolfsokta> Todays topics: DGW implementation, segfault, Q&A, feedback on IRC
[16:01] <@Wolfsokta> Just to set the stage here, this is a developer meeting where developers that have contributed source code to the Ravencoin project can meet and chat about items they are working on. Please be respectful to one another. For the sake of staying on target, please limit interactions to questions and comments on code or projects that you are working on. Any time left over at the end can be opened up for general Q&A.
[16:02] <@Wolfsokta> FYI - I'm RavencoinDev, and lets get started.
[16:03] <@Wolfsokta> @Tron, can you talk about where we are at with DGW on testnet and mainnet?
[16:03] <@Tron> Sure.
[16:03] can someone volunteer to take notes and post also?
[16:03] <@Tron> We are building binaries that will activate DGW-180 at block 338778
[16:04] <@Tron> It looks back 180 blocks to calculate the diff.
[16:04] I will copy the text from the meeting into a file that can be archived later. I can also make summary notes after like BTC core does.
[16:04] I'll save a log of the whole meeting and can post it on the subreddit thread.
[16:04] <@Wolfsokta> We have setup testnet4 in order to test the new binaries.
[16:04] great
[16:05] <@Wolfsokta> We plan to release the binaries later today.
[16:05] @Tron have you looked into the timestamp attack concerns of DGW?
[16:06] <@Tron> Yes. And for that reason, we've tightened up the timestamps that will be accepted for valid blocks.
[16:06] <@Tron> Moved from 2h to 12 minutes.
[16:06] nice
[16:06] Oh wow okay
[16:06] <@Tron> Its also the reason we went from 60 blocks (lookback) to 180 blocks.
[16:07] why would 2h ever be acceptable? lol
[16:07] 2h was originally used for daylight savings shenanigans I believe
[16:07] <@Tron> It was from bitcoin, and it factors in clock skew, and variance in finding blocks on 10 minute intervals, and block propagation time.
[16:07] makes sense
[16:08] what about the segmentation fault when reindexing?
[16:08] any fix yet?
[16:08] @Tron 12 minutes seems to be pretty small window for clock skew
[16:08] I assume it was chosen due to 1/10th scaling from BTC?
[16:09] <@Wolfsokta> Not yet ruski, we'll cover that in a bit.
[16:09] <@Tron> We did divide existing by 10.
[16:10] <@Wolfsokta> Any further questions about DGW on testnet or on mainnet?
[16:10] What block is it activating on mainnet?
[16:10] <@Wolfsokta> 338778
[16:11] And will there be the need to update binaries twice (for DGW fork and asset layer fork)?
[16:11] <@Tron> We are activating DGW by block height because headers sync first, and the BIP9 activation flag sets a flag, and we need to look at either block height or version to know which diff algo.
[16:11] <@Wolfsokta> Calculated to be near the end of the month so we have some time with DGW on testnet.
[16:11] Someone on discord asked this a while back, but why Was DGW chosen over something like digishield or anyother algo
[16:11] <@Tron> And block version can be changed (tampering) and still make it on the chain.
[16:12] Binaries will need to be updated as more asset layer stuff get completed and tested. Not by the end of the month though.
[16:12] <@Tron> We looked at DGW and LWMA. LWMA has a lot of constants that must be tuned right.
[16:13] <@Tron> We were impressed with the amount of work on LWMA to analyze how it responds, but it wasn't straightforward to understand the nuances of how/why it works.
[16:13] zawy was in the #development channel on Discord. He's an expert on DAAs. I'm sure he would help with tuning LWMA if you asked.
[16:14] <@Tron> Either will be much better that what we have. Even at the extremes, it will adjust smoothly.
[16:14] Are there any issues or comments on the DGW code that should be addressed?
[16:14] @devs in general
[16:15] <@Wolfsokta> Thanks @brianmct, we did look extensively at the DGW code to ensure we weren't going to see the same issues that happened to Verge.
[16:16] so i guess you would have to make way more blocks with false timestamps to be able to exploit our version of dgw right?
[16:16] because of the 12 minute timestamp thing?
[16:16] <@Wolfsokta> With X16R, and with the changes Tron talked about we feel confident that this will address the swings without being able to be exploited.
[16:17] nice
[16:17] @russki Yeah, pretty much.
[16:17] verge is a different type of situation - but overall asics and mining are a risk always
[16:18] <@Wolfsokta> Okay, anything else on the difficulty targeting change?
[16:19] <@Wolfsokta> Cool, blondfrogs wanted to talk about subassets that were added.
[16:19] ooh yeah i saw those github commits
[16:19] looking good
[16:19] We also want to let everyone know that you can now create sub assets with the new binaries that will be posted soon. You can create these subassets using the issue rpc call. Qt will be built shortly. This will allow users to make an asset PARENT
[16:20] <@Wolfsokta> Basic overview. If you own an asset you can create sub-assets by including a '/
[16:20] nice
[16:20] And then make any of the following PARENT/A PARENT/B .... PARENT/Z
[16:20] <@Tron> We'll post a FAQ on assets later today.
[16:21] <@Wolfsokta> And it only is 100 Raven for a subasset
[16:21] on testnetv4 it still says asset activation status: waiting
[16:21] why?
[16:21] <@Tron> Yep, it needs to be voted in.
[16:21] <@Wolfsokta> We wanted to test the BIP9 activation process again as well. The more testing the better.
[16:21] We wanted to make sure that we follow the same process the Mainnet is going to go through.
[16:21] ok nice
[16:22] <@Wolfsokta> Any questions about subassets?
[16:23] are they unique?
[16:23] <@Tron> No
[16:23] <@Wolfsokta> Yes, they behave the same way as a normal asset, just live under an owned asset.
[16:23] <@Tron> Maybe I misunderstood the question. Unique with parent.
[16:23] Each subasset can have their own number issued? So PARENT/A can have 1,000 and PARENT/B can be 50?
[16:23] yes
[16:23] oooh ok that makes more sense
[16:23] <@Wolfsokta> Exactly thanks traysi
[16:24] <@Tron> And, not the same thing as "Unique Assets"
[16:24] <@Wolfsokta> The individual unique asset support is included in an upcoming phase.
[16:25] Moving onto the Segfault issue ----------------------->>>>>>>>>>> SEGFAULT
[16:25] Are we able to changes the properties of subassets after they have been created? Or is something like that specified when creating them?
[16:25] <@Tron> Yes
[16:25] can sub-assets be reassigned to other addresses while retaining control of the parent asset elsewhere?
[16:25] So basically it has all the features of a normal asset, but live under an asset's top-level namespace?
[16:25] satoshi corbie @russkidooski
[16:25] So basically it has all the features of a normal asset, but live under an asset's top-level namespace?
[16:26] <@Tron> Sub-assets are identical to assets after creation.
[16:26] <@Tron> Just cheaper to create, and in your "owned" namespace.
[16:26] Okay cool
[16:26] will subassets eventually have a unqiue tag? eg ASSET/SUB:1
[16:26] We have found an issue with our testnet binaries and are still looking to the issue. The issue presents itself when a user performs a reindexing of the chain. We think we have pinpointed the where the problem is and are currently working a fix. This fix will be out shortly.
[16:26] plan is to make default reissue=true and units=0 and allow increase in units on reissue
[16:26] How much is it going to be for a sub-asset?
[16:27] 100
[16:27] <@Wolfsokta> Okay, let's now focus on the SegFault issue that was discovered by Under.
[16:28] do you know what the issue was?
[16:28] <@Wolfsokta> It seems to be a build problem with the boost library.
[16:28] Still looking into though. :)
[16:29] <@Wolfsokta> We have been able to reproduce it on linux internally with 2.0.3
[16:29] yea i get the same issue on windows 10
[16:30] I saw a Bitcoin thread a while back about the seg fault error. I had it because I had conflicting versions of BDB
[16:30] static compiled on ubuntu 18.04
[16:30] <@Wolfsokta> We really appreciate you guys pulling down master and helping test.
[16:30] @Trap we will look into that also
[16:30] no problem, im just curious lol
[16:32] <@Wolfsokta> We haven't been able to build a windows version that doesn't have the segfault issue.
[16:32] <@Tron> We're dropping Windows support ;)
[16:32] lol
[16:33] Just finished setting up a new Windows test environment so we can test and validate the solution as we are working on it.
[16:33] The bdb issue is a known issue that has been around for some time. We are pretty certain it is a boost library issue, and are working quickly to get a windows build that fixes the issue.
[16:34] what did you guys do to fix the linux version?
[16:34] Once we have binaries for all supported platforms ready, hopefully tonight. No promises. We will make an announcement
[16:34] The issue has been fixed on Linux and Mac though?
[16:34] (oops sorry already answered)
[16:34] <@Wolfsokta> If anybody else gets there first with Windows please let us know what you found.
[16:34] Built the binairies on a Ubuntu 16.04 box.
[16:34] that was it?
[16:35] Yeah, we think so. 16.04 has boost 1.58 which seems to fix the issue. The build on 18.04 use boost 1.67 which seems to cause the issue.
[16:35] is there a boost 1.58 repo on 18.04?
[16:35] 18.04 used 1.65***
[16:36] I've built with boost 1.68 on arch Linux
[16:36] It worked
[16:37] wallet 2.0.x?
[16:37] @Trap, the issue is when -reindex is used.
[16:37] Oh sorry my bad
[16:37] Wallet 2.0.3
[16:38] <@Wolfsokta> For those that joined late we're discussing
[16:38] 1 sec im going to boot into ubuntu and try compiling with 1.58 on 18.04
[16:39] Any other questions pertaining to the segfault?
[16:40] <@Wolfsokta> Alright, thanks everybody. Before we start the Q&A I would like to get some quick feedback on using IRC for this meeting.
[16:41] If we're going to use IRC we should take some measures to at least hide people's IPs when they join
[16:42] Yea. It is very hard to read this back.
[16:42] Also no message history
[16:42] If you disconnect and reconnect
[16:42] <@Tron> I'll throw in a vote for Discord.
[16:43] <@Wolfsokta> If you use a decent IRC client instead of the website it's not bad.
[16:43] Some of us used a VPN before we connected to IRC
[16:43] If needed we can restrict channel to Developer roles, etc for the developer meeting and open it up for general Q&A
[16:43] poll
[16:43] Make a discord when only mods can submit links
[16:43] Where*
[16:45] Discord won the poll 5 to 2
[16:45] <@Wolfsokta> There are also a lot of IRC tools that can be used to track the meetings.
[16:45] we know
[16:46] <@Wolfsokta> We also want any developer to be able to speak.
[16:48] <@Wolfsokta> We're open to try Discord next week.
[16:48] <[kai]> perhaps you could even get a feed from this irc to discord?
[16:49] <[kai]> a feed would enable discordians to view the chat, but only contribute if they take the extra steps to come here.
[16:49] <@Wolfsokta> That's a good idea kai... Has anybody seen that working?
[16:50] <[kai]>
[16:50] <[kai]> im sure you could make this a one way deal.
[16:51] <@Wolfsokta> I like that idea, let's try that for next week. So we'll meet here in IRC again, but it should be broadcast to Discord.
[16:53] <@Wolfsokta> Okay, we'll go with IRC next week with the broadcast to discord and re-visit for next week.
[16:54] <@Wolfsokta> Okay, let's do open Q&A for the next few mins.
[16:54] <[kai]> just a quickey, more for my curioisty, did you look at digishield?
[16:54] <[kai]> DGW solution seems solid.
[16:55] <[kai]> was just curious if it was one of the four solutions you looked at.
[16:55] <@Wolfsokta> Tron is answering... Any others Q?
[16:55] <@Tron> We briefly looked at Digishield, but our analysis was between DGW and LWMA.
[16:55] <[kai]> right on.
[16:56] <[kai]> cheers guys, see you next time.
[16:56] OPen the gates for the last 4 minutes for any other questions?
[16:58] <@Wolfsokta> Alright, thank you all for being here today and please join the development effort with us. If you have an idea, or a fix for an issue write it up and submit a pull request.
[16:59] <@Wolfsokta> Thanks again for all those that have contributed their time and effort to make Ravencoin successful. We have the BEST community.
[16:59] ^
6:59] You devs are pretty cool
[16:59] did the burn get discussed?
[16:59] <@Wolfsokta> Special thanks to Bruce, really glad you could make it with the short notice.
[17:00] <@Tron> Thanks everyone!
submitted by __pathfinder__ to Ravencoin [link] [comments]

Bitcoin Unlimited - Bitcoin Cash edition has just been released

Download the latest Bitcoin Cash compatible release of Bitcoin Unlimited (, August 17th, 2018) from:
This release is a major release which is compatible with the Bitcoin Cash compatible with the Bitcoin Cash specifications you could find here:
A subsequent release containing the implementation of the November 2018 specification will be released soon after this one.
List of notable changes and fixes to the code base:
Release notes:
Ubuntu PPA repository for BUcash has been updated
submitted by s1ckpig to Bitcoincash [link] [comments]

Linux bitcoin mining rig Radeon 5850 Ubuntu -2 Setting up .bitcoin folder Bitcoin Install and Update on Ubuntu Linux ( my experience ) How to install BFGminer on Ubuntu 17.04 How to install Bitcoin Core wallet in any Linux distribution

** Add config to bitcoin.conf file ** rpcuser=username: rpcpassword=password: testnet=1: rpcport=8332: rpcallowip= rpcallowip= server=1 ** Start bitcoind ** bitcoind --daemon ** If bitcoind is already started ** ps -e grep bitcoin // returns pid: kill -9 <pid> bitcoind & ** Test bitcoind is running and working ... Bitcoin config file to setup bitcoin node in testnet network in ubuntu. Ask Question Asked 2 years, 6 months ago. Active 2 years, 6 months ago. Viewed 6k times 1. 3. I am new to blockchain, I want to setup my node in testnet network in my ubuntu machine. I am using this below mentioned bitcoin.conf file. Is this the correct format to sync the node faster? Or I need to do the changes in this ... In this post, I show you how to set up your own Bitcoin Core for Testnet, and learn how to work with your own wallet and address for Bitcoin beginners (developers). Prerequisite Settings. Here I’ll run Bitcoin Core on Ubuntu 18.04 in Microsoft Azure. Bitcoin Core needs a large disk to store blocks. Then I expanded disks to around 1 TB by ... How can I run Bitcoin core testnet version on ubuntu 16.04 platform ? I am getting so many reference about how to run bitcoin core mainnet but it will take around 20 days to synchronize with the network as per my bandwidth and also will take my half of the HDD. So I opt for Testnet. Can someone explain me how to insatll bitcoin core testnet on ... # bitcoin-testnet-box docker image # Ubuntu 14.04 LTS (Trusty Tahr) FROM ubuntu:14.04: LABEL maintainer= "Sean Lavine <[email protected]>" # add bitcoind from the official PPA # install bitcoind (from PPA) and make: RUN apt-get update && \ apt-get install --yes software-properties-common && \ add-apt-repository --yes ppa:bitcoin/bitcoin && \ apt-get update && \ apt-get install --yes bitcoind ...

[index] [26114] [4360] [3600] [39546] [8190] [2076] [37762] [15039] [50323] [19234]

Linux bitcoin mining rig Radeon 5850

Creating a Local Bitcoin Testnet / Regtest - Programming Bitcoin - Duration: 23:19. Programming Bitcoin 19,911 views. 23:19. The Opposite of Infinity - Numberphile - Duration: 15:05. ... This video explains the installation procedure of BFGminer on Ubuntu. The BFGminer is a Bitcoin miner software which is multi-threaded multi-pool GPU, FPGA and ASIC mining support. Using Ubuntu 10.4, bitcoin 0.3.24, I show my installation of Bitcoin. These are the commands to install bitcoin; sudo apt-add-repository ppa:stretch/bitcoin sudo apt-get update sudo apt-get ... Creating a Local Bitcoin Testnet / Regtest - Programming Bitcoin - Duration: 23:19. Programming Bitcoin 19,060 views. 23:19. How to Install Ubuntu 18.04 LTS on VirtualBox in Windows 10 / Windows ... Ubuntu -2 Setting up .bitcoin folder Commands, cd ~/ mkdir .bitcoin cd .bitcoin nano bitcoin.conf server=1 daemon=1 testnet=0 rpcuser=UNIQUE_RPC_USERNAME rpcpassword=UNIQUE_RPC_PASSWORD.