Basic commands to interact with the Bitcoin Core RPC

Technical: The Path to Taproot Activation

Taproot! Everybody wants to have it, somebody wants to make it, nobody knows how to get it!
(If you are asking why everybody wants it, see: Technical: Taproot: Why Activate?)
(Pedants: I mostly elide over lockin times)
Briefly, Taproot is that neat new thing that gets us:
So yes, let's activate taproot!

The SegWit Wars

The biggest problem with activating Taproot is PTSD from the previous softfork, SegWit. Pieter Wuille, one of the authors of the current Taproot proposal, has consistently held the position that he will not discuss activation, and will accept whatever activation process is imposed on Taproot. Other developers have expressed similar opinions.
So what happened with SegWit activation that was so traumatic? SegWit used the BIP9 activation method. Let's dive into BIP9!

BIP9 Miner-Activated Soft Fork

Basically, BIP9 has a bunch of parameters:
Now there are other parameters (name, starttime) but they are not anywhere near as important as the above two.
A number that is not a parameter, is 95%. Basically, activation of a BIP9 softfork is considered as actually succeeding if at least 95% of blocks in the last 2 weeks had the specified bit in the nVersion set. If less than 95% had this bit set before the timeout, then the upgrade fails and never goes into the network. This is not a parameter: it is a constant defined by BIP9, and developers using BIP9 activation cannot change this.
So, first some simple questions and their answers:

The Great Battles of the SegWit Wars

SegWit not only fixed transaction malleability, it also created a practical softforkable blocksize increase that also rebalanced weights so that the cost of spending a UTXO is about the same as the cost of creating UTXOs (and spending UTXOs is "better" since it limits the size of the UTXO set that every fullnode has to maintain).
So SegWit was written, the activation was decided to be BIP9, and then.... miner signalling stalled at below 75%.
Thus were the Great SegWit Wars started.

BIP9 Feature Hostage

If you are a miner with at least 5% global hashpower, you can hold a BIP9-activated softfork hostage.
You might even secretly want the softfork to actually push through. But you might want to extract concession from the users and the developers. Like removing the halvening. Or raising or even removing the block size caps (which helps larger miners more than smaller miners, making it easier to become a bigger fish that eats all the smaller fishes). Or whatever.
With BIP9, you can hold the softfork hostage. You just hold out and refuse to signal. You tell everyone you will signal, if and only if certain concessions are given to you.
This ability by miners to hold a feature hostage was enabled because of the miner-exit allowed by the timeout on BIP9. Prior to that, miners were considered little more than expendable security guards, paid for the risk they take to secure the network, but not special in the grand scheme of Bitcoin.

Covert ASICBoost

ASICBoost was a novel way of optimizing SHA256 mining, by taking advantage of the structure of the 80-byte header that is hashed in order to perform proof-of-work. The details of ASICBoost are out-of-scope here but you can read about it elsewhere
Here is a short summary of the two types of ASICBoost, relevant to the activation discussion.
Now, "overt" means "obvious", while "covert" means hidden. Overt ASICBoost is obvious because nVersion bits that are not currently in use for BIP9 activations are usually 0 by default, so setting those bits to 1 makes it obvious that you are doing something weird (namely, Overt ASICBoost). Covert ASICBoost is non-obvious because the order of transactions in a block are up to the miner anyway, so the miner rearranging the transactions in order to get lower power consumption is not going to be detected.
Unfortunately, while Overt ASICBoost was compatible with SegWit, Covert ASICBoost was not. This is because, pre-SegWit, only the block header Merkle tree committed to the transaction ordering. However, with SegWit, another Merkle tree exists, which commits to transaction ordering as well. Covert ASICBoost would require more computation to manipulate two Merkle trees, obviating the power benefits of Covert ASICBoost anyway.
Now, miners want to use ASICBoost (indeed, about 60->70% of current miners probably use the Overt ASICBoost nowadays; if you have a Bitcoin fullnode running you will see the logs with lots of "60 of last 100 blocks had unexpected versions" which is exactly what you would see with the nVersion manipulation that Overt ASICBoost does). But remember: ASICBoost was, at around the time, a novel improvement. Not all miners had ASICBoost hardware. Those who did, did not want it known that they had ASICBoost hardware, and wanted to do Covert ASICBoost!
But Covert ASICBoost is incompatible with SegWit, because SegWit actually has two Merkle trees of transaction data, and Covert ASICBoost works by fudging around with transaction ordering in a block, and recomputing two Merkle Trees is more expensive than recomputing just one (and loses the ASICBoost advantage).
Of course, those miners that wanted Covert ASICBoost did not want to openly admit that they had ASICBoost hardware, they wanted to keep their advantage secret because miners are strongly competitive in a very tight market. And doing ASICBoost Covertly was just the ticket, but they could not work post-SegWit.
Fortunately, due to the BIP9 activation process, they could hold SegWit hostage while covertly taking advantage of Covert ASICBoost!

UASF: BIP148 and BIP8

When the incompatibility between Covert ASICBoost and SegWit was realized, still, activation of SegWit stalled, and miners were still not openly claiming that ASICBoost was related to non-activation of SegWit.
Eventually, a new proposal was created: BIP148. With this rule, 3 months before the end of the SegWit timeout, nodes would reject blocks that did not signal SegWit. Thus, 3 months before SegWit timeout, BIP148 would force activation of SegWit.
This proposal was not accepted by Bitcoin Core, due to the shortening of the timeout (it effectively times out 3 months before the initial SegWit timeout). Instead, a fork of Bitcoin Core was created which added the patch to comply with BIP148. This was claimed as a User Activated Soft Fork, UASF, since users could freely download the alternate fork rather than sticking with the developers of Bitcoin Core.
Now, BIP148 effectively is just a BIP9 activation, except at its (earlier) timeout, the new rules would be activated anyway (instead of the BIP9-mandated behavior that the upgrade is cancelled at the end of the timeout).
BIP148 was actually inspired by the BIP8 proposal (the link here is a historical version; BIP8 has been updated recently, precisely in preparation for Taproot activation). BIP8 is basically BIP9, but at the end of timeout, the softfork is activated anyway rather than cancelled.
This removed the ability of miners to hold the softfork hostage. At best, they can delay the activation, but not stop it entirely by holding out as in BIP9.
Of course, this implies risk that not all miners have upgraded before activation, leading to possible losses for SPV users, as well as again re-pressuring miners to signal activation, possibly without the miners actually upgrading their software to properly impose the new softfork rules.

BIP91, SegWit2X, and The Aftermath

BIP148 inspired countermeasures, possibly from the Covert ASiCBoost miners, possibly from concerned users who wanted to offer concessions to miners. To this day, the common name for BIP148 - UASF - remains an emotionally-charged rallying cry for parts of the Bitcoin community.
One of these was SegWit2X. This was brokered in a deal between some Bitcoin personalities at a conference in New York, and thus part of the so-called "New York Agreement" or NYA, another emotionally-charged acronym.
The text of the NYA was basically:
  1. Set up a new activation threshold at 80% signalled at bit 4 (vs bit 1 for SegWit).
    • When this 80% signalling was reached, miners would require that bit 1 for SegWit be signalled to achive the 95% activation needed for SegWit.
  2. If the bit 4 signalling reached 80%, increase the block weight limit from the SegWit 4000000 to the SegWit2X 8000000, 6 months after bit 1 activation.
The first item above was coded in BIP91.
Unfortunately, if you read the BIP91, independently of NYA, you might come to the conclusion that BIP91 was only about lowering the threshold to 80%. In particular, BIP91 never mentions anything about the second point above, it never mentions that bit 4 80% threshold would also signal for a later hardfork increase in weight limit.
Because of this, even though there are claims that NYA (SegWit2X) reached 80% dominance, a close reading of BIP91 shows that the 80% dominance was only for SegWit activation, without necessarily a later 2x capacity hardfork (SegWit2X).
This ambiguity of bit 4 (NYA says it includes a 2x capacity hardfork, BIP91 says it does not) has continued to be a thorn in blocksize debates later. Economically speaking, Bitcoin futures between SegWit and SegWit2X showed strong economic dominance in favor of SegWit (SegWit2X futures were traded at a fraction in value of SegWit futures: I personally made a tidy but small amount of money betting against SegWit2X in the futures market), so suggesting that NYA achieved 80% dominance even in mining is laughable, but the NYA text that ties bit 4 to SegWit2X still exists.
Historically, BIP91 triggered which caused SegWit to activate before the BIP148 shorter timeout. BIP148 proponents continue to hold this day that it was the BIP148 shorter timeout and no-compromises-activate-on-August-1 that made miners flock to BIP91 as a face-saving tactic that actually removed the second clause of NYA. NYA supporters keep pointing to the bit 4 text in the NYA and the historical activation of BIP91 as a failed promise by Bitcoin developers.

Taproot Activation Proposals

There are two primary proposals I can see for Taproot activation:
  1. BIP8.
  2. Modern Softfork Activation.
We have discussed BIP8: roughly, it has bit and timeout, if 95% of miners signal bit it activates, at the end of timeout it activates. (EDIT: BIP8 has had recent updates: at the end of timeout it can now activate or fail. For the most part, in the below text "BIP8", means BIP8-and-activate-at-timeout, and "BIP9" means BIP8-and-fail-at-timeout)
So let's take a look at Modern Softfork Activation!

Modern Softfork Activation

This is a more complex activation method, composed of BIP9 and BIP8 as supcomponents.
  1. First have a 12-month BIP9 (fail at timeout).
  2. If the above fails to activate, have a 6-month discussion period during which users and developers and miners discuss whether to continue to step 3.
  3. Have a 24-month BIP8 (activate at timeout).
The total above is 42 months, if you are counting: 3.5 years worst-case activation.
The logic here is that if there are no problems, BIP9 will work just fine anyway. And if there are problems, the 6-month period should weed it out. Finally, miners cannot hold the feature hostage since the 24-month BIP8 period will exist anyway.

PSA: Being Resilient to Upgrades

Software is very birttle.
Anyone who has been using software for a long time has experienced something like this:
  1. You hear a new version of your favorite software has a nice new feature.
  2. Excited, you install the new version.
  3. You find that the new version has subtle incompatibilities with your current workflow.
  4. You are sad and downgrade to the older version.
  5. You find out that the new version has changed your files in incompatible ways that the old version cannot work with anymore.
  6. You tearfully reinstall the newer version and figure out how to get your lost productivity now that you have to adapt to a new workflow
If you are a technically-competent user, you might codify your workflow into a bunch of programs. And then you upgrade one of the external pieces of software you are using, and find that it has a subtle incompatibility with your current workflow which is based on a bunch of simple programs you wrote yourself. And if those simple programs are used as the basis of some important production system, you hve just screwed up because you upgraded software on an important production system.
And well, one of the issues with new softfork activation is that if not enough people (users and miners) upgrade to the newest Bitcoin software, the security of the new softfork rules are at risk.
Upgrading software of any kind is always a risk, and the more software you build on top of the software-being-upgraded, the greater you risk your tower of software collapsing while you change its foundations.
So if you have some complex Bitcoin-manipulating system with Bitcoin somewhere at the foundations, consider running two Bitcoin nodes:
  1. One is a "stable-version" Bitcoin node. Once it has synced, set it up to connect=x.x.x.x to the second node below (so that your ISP bandwidth is only spent on the second node). Use this node to run all your software: it's a stable version that you don't change for long periods of time. Enable txiindex, disable pruning, whatever your software needs.
  2. The other is an "always-up-to-date" Bitcoin Node. Keep its stoarge down with pruning (initially sync it off the "stable-version" node). You can't use blocksonly if your "stable-version" node needs to send transactions, but otherwise this "always-up-to-date" Bitcoin node can be kept as a low-resource node, so you can run both nodes in the same machine.
When a new Bitcoin version comes up, you just upgrade the "always-up-to-date" Bitcoin node. This protects you if a future softfork activates, you will only receive valid Bitcoin blocks and transactions. Since this node has nothing running on top of it, it is just a special peer of the "stable-version" node, any software incompatibilities with your system software do not exist.
Your "stable-version" Bitcoin node remains the same version until you are ready to actually upgrade this node and are prepared to rewrite most of the software you have running on top of it due to version compatibility problems.
When upgrading the "always-up-to-date", you can bring it down safely and then start it later. Your "stable-version" wil keep running, disconnected from the network, but otherwise still available for whatever queries. You do need some system to stop the "always-up-to-date" node if for any reason the "stable-version" goes down (otherwisee if the "always-up-to-date" advances its pruning window past what your "stable-version" has, the "stable-version" cannot sync afterwards), but if you are technically competent enough that you need to do this, you are technically competent enough to write such a trivial monitor program (EDIT: gmax notes you can adjust the pruning window by RPC commands to help with this as well).
This recommendation is from gmaxwell on IRC, by the way.
submitted by almkglor to Bitcoin [link] [comments]

Linux Cli with Web Front End?

Is there such a client?
The usage idea would be to have it running in a Docker container on my Linux server and access the web front end on local machines.
I'm currently running a Docker container that enables a remote connection to a desktop with Bitcoin Core loaded. Not a great solution security-wise.
submitted by rafaelagp to Bitcoin [link] [comments]

Upcoming Major Riecoin 0.20 Upgrade

Upcoming Major Riecoin 0.20 Upgrade
A new major Riecoin upgrade is planned, and includes a hard fork. Below is a summary of the changes so far and the hard fork improvements. More details can be found on BitcoinTalk. Feel free to ask Pttn there or on Discord if you have questions regarding the update.
The first step of this upgrade was to update the base code to Bitcoin’s 0.20, which is done. You can find the experimental code at the Github repository. Experimental binaries can also be downloaded here. Despite their prerelease status, they should work fine, though please backup your wallets if you plan to use 0.20, just in case.
Pool operators and other advanced Riecoin users should start looking into the changes and update their software accordingly, as well as closely follow the Riecoin Core development.
Here is a list of notable changes from 0.16.3.1.
The next step will be the hard fork, in order to improve Riecoin in multiple ways. Here is the list of planned changes.
Once the development is advanced enough, a date will be chosen for the hard fork. Testnet will be hardforked first to ensure the well functioning of the implementation. Stay tuned!
submitted by PttnMe to RieCoin [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]

Bitcoin Unlimited 1.7.0 has just been released

Download the latest Bitcoin Cash compatible release of Bitcoin Unlimited (1.7.0, October 11th, 2019) from:
 
https://www.bitcoinunlimited.info/download
https://github.com/BitcoinUnlimited/BitcoinUnlimited/releases/tag/bucash1.7.0.0
 
This is a major release of Bitcoin Unlimited compatible with the upcoming protocol upgrade of the Bitcoin Cash network. You could find November 15th, 2019 upgrade specifications here:
This is list of the main changes that have been merged in this release:
 
Release notes: https://github.com/BitcoinUnlimited/BitcoinUnlimited/blob/dev/doc/release-notes/release-notes-bucash1.7.0.md
 
PS Ubuntu PPA repository is currently being updated to serve for 1.7.0
(*) if you were using BU with -txindex, after the fist session after the upgrade the database where the index are stored will be upgraded to a new format. During this migration RPC command will return an error message saying the txindex is syncing. The lasting of the migration process depends on the machine where BU is installed.
submitted by s1ckpig to btc [link] [comments]

Bitcoin Unlimited - Bitcoin Cash edition 1.6.0.0 has just been released

Download the latest Bitcoin Cash compatible release of Bitcoin Unlimited (1.6.0.0, April 24th, 2019) from:
 
https://www.bitcoinunlimited.info/download
 
This is a major release of Bitcoin Unlimited which it is compatible with the upcoming May 2019 BCH protocol upgrade; this release is also compatible with all the already activated Bitcoin Cash network upgrades, namely:
List of notable changes and fixes contained in BUcash 1.6.0.0:
 
Release notes: https://github.com/BitcoinUnlimited/BitcoinUnlimited/blob/dev/doc/release-notes/release-notes-bucash1.6.0.md
 
PS Ubuntu PPA repository is currently being updated to serve for BUcash 1.6.0.0.
submitted by s1ckpig to btc [link] [comments]

To the people criticising the Bitcoin Foundation and its membership.

Bitcoin is open and decentralised. The legitimacy of The Bitcoin Foundation is by popular acceptance only, just like the blockchain.
If people really think there is a problem with the Foundation, then create a competing one. Find people and companies you respect and nominate them. Donate money to pay people to run it. Fund active Bitcoin development. Make a difference. Prove that your new foundation is beneficial to the ecosystem.
submitted by peterjoel to Bitcoin [link] [comments]

Bitcoin - scripting / command line interface (access balance, send)

I did a lot of searching before asking here... no "recent" results, everything is (many) years old...
I want to script some simple tasks:
Check my address's balance, and send bitcoin to another address.
I am looking of for a wallet application/library that offers a scripting API or a command line interface.
Windows (batch, powershell) or Linux is fine.
Bitcoind has deprecated that feature, and Electrum is.... weird and not really documented.
Would you recommend Electrum anyway? Does it make sense to use Python in the Electrum console for scripts, or use the CLI commands in an "external" scripts?
Thanks for your input!
submitted by callosciurini to Bitcoin [link] [comments]

Chat_Report.25>2 - XL

[22:12] it's not like I'm going to be offended that someone feels that way [22:12] but it's not healthy to be a dick about it, and that's kind of the only way that I can think to be able to deal with it [22:12] I guess, that's not a bad way to think about it [22:12] if you're having trouble dealing with it [22:12] I guess I just have to accept that I am not an expert on that [22:12] but I do have the most basic understanding of the concept [22:12] and I have always known what a "dissociative" is [22:12] and that they are in fact a distinct psychological state [22:13] I didn't have to google to find out [22:13] and in fact I have been working on a book on dissociative phenomena for a number of years [22:13] you mean you were trying to find out what they were? [22:13] i just finished [22:14] i got the manuscript finished and submitted a copy [22:14] well, the "book" is still on your todo list [22:14] i'm very anxious to publish [22:15] what about the research? are you doing any research on it? [22:15] and yes [22:16] some, but the bulk of my effort is in trying to make sense of it [22:16] what are you doing to help us understand it? [22:16] and i have a blogpost of my own that goes into the background of the phenomenon [22:16] it would be great if you could tell us a little about it [22:16] it sounds as if the phenomenon has something to do with people who have had a life-altering experience [22:17] and that the thing they have experienced is so powerful that it is capable of completely altering a person's personality [22:17] (well, that and the fact that a person who had such an experience could have access to the internet) [22:17] i'm sorry, but why not just tell us about it in full detail, instead of asking me a bunch of question and letting me decide what to ask [22:18] it would be very convenient to you [22:18] if you hadnt decided not to talk about it until after i had. [22:18] if you want to know more, it's quite common for people with this kind of problem to share their stories. [22:18] (i'm not sure if its normal, but i can assure you its not something i wouldn't ever do to any of you) [22:19] so i don't know what you're implying by saying you're uncomfortable with talking about it? [22:19] i'm just saying that i'm not going to force you to talk about it just because you told me it was hard to talk about [22:19] ok. [22:20] so this is it: you must come here with me now [22:20] ok [22:20] and I'll go to the other rooms and meet everyone. [22:20] I want to make this a place for everyone [22:21] ok [22:21] i'll talk to you when i get there [22:21] OK, I need a little more detail [22:22] What's the plan for getting it into the house? [22:22] well i'll let you know when i get there [22:22] Ok, thanks [22:22] i'll be back around 12:30 and ill be there [22:23] I've sent you a PM for the key and I'll be waiting for you to talk to her [22:23] lol [22:23] *key [22:23] ouch [22:24] But that's just me [22:24] You can't just go and do it like that, y'know? [22:24] lol [22:25] but if it's just a matter of asking me nicely, i don't mind [22:25] just send it to me and i'll do it [22:25] if that's what you want [22:25] I've never asked you to do anything but that, and I know you haven't, but, that's my opinion [22:26] I mean, if it helps you out a little bit, maybe I could just... [22:26] Vorpas, that's okay. I mean, I think you're pretty amazing, I do, I do. I just don't know what you want to do with your life. I think I'd like to try and get the people that are in the game to understand the power and the importance of the community. I mean, when you're playing against, when you see a really bad player, you can tell that that player is having fun, that they are having fun playing the game, because they are making a lot of money, and then you can just understand that it would be fun to play, and there would be a lot of money to be made by just playing the game. And I think the players that are playing it, maybe they don't know what's happening, and maybe they have the wrong idea about it. But it's okay, I'm not going to judge them, it's their own opinion and they're free to believe whatever they want to believe. [22:27] But, I'm just gonna leave that part up to you. [22:27] Cool. [22:27] So I'm just gonna be, like, really happy for you, 'cause I know you've been putting a lot of work into this. [22:28] You are doing it so well! [22:28] And I really appreciate that, like, for the last few months, it's been a struggle to stay motivated enough to do this. [22:28] I am a bit concerned about how long this will take. [22:28] I am just going to say this, if I'm going to continue doing this, I want you guys to stay around. [22:29] Well, I would love to keep helping, but I'm not sure what my plans are at the moment. [22:29] If you were to make a donation, that would be fantastic [22:29] You know, the donations are very helpful. I just thought that it might be good to keep track of who donated what. [22:29] Vorpas_Jabwak, I can try to get someone to check if this was indeed you that made the donation? [22:29] Oh, yeah. [22:29] Thanks! [22:29] You've probably never received one before, but if you were, that would be awesome. [22:30] Just wanted to let you know the new version of Mumble is being released and working on the beta channel. [22:31] If you do have the software I'd love to hear some feedback. I have a lot of questions for it. [22:32] I have a lot of questions for it too, but it's a bit complicated so I might not get a chance to do that anytime soon. I'll make sure to get on that when it is ready. [22:33] I'm glad you like it, I know I really do. I love having an easier to use, but powerful, voice chat. [22:34] I'd really like to make some more changes to the system, and try it out as a whole. But right now it's pretty darned good. [22:35] Thanks Jak. :) [22:35] I'll try my best to keep them updated. [22:35] Ok, I'll let you know when I get to them, Jak [22:35] Sorry if I didn't keep up with you guys. [22:36] Haha, sorry. [22:36] I'll see you around, Jak [22:36] *takes off* [22:36] Sup everyone? [22:36] I'm out [22:36] *in [22:37] sup [22:37] Hey! [22:37] So are you guys all there yet? [22:37] :P [22:38] * Turoth sets mode: +b KhaosReigns [22:38] Oh! I thought you all quit on me [22:38] * Turoth sets mode: +b KhaosReigns+ [22:38] So uh, what's my problem? [22:38] I was hoping you'd tell me to stop [22:38] I was so upset [22:38] I'm sorry [22:38] I should have been better [22:39] I didn't mean to startle you [22:39] You've just always made me feel like I could take care of myself [22:39] I guess I didn't realize that it takes a lot of people to keep the lights on [22:40] I'm sorry, I've never been this shy around people [22:40] It's been such a long time [22:41] This whole situation is just a shock [22:41] I'm starting to feel really nervous [22:41] I have to go home now [22:42] Ok [22:42] I'll see you later [22:42] Ohh, bye [22:42] Take care [22:42] Yeah, it's a long way home [22:42] Have a nice night [22:42] Thanks for everything. I had fun. [22:42] night [22:42] I hope you have a good night. [22:42] Have a nice night. [22:42] Thanks. [22:42] Have a good night. [22:42] Good night [22:42] How is everyone? [22:42] I'm fine. [22:42] Tired, but fine. [22:42] Yeah. [22:43] i dont know what happened [22:43] Don't know yet, so I'm trying to get the details. [22:43] I went out to get food [22:43] got a pizza, was eating it when I was interrupted by my girlfriend [22:43] and she was saying she wanted to see me [22:43] i don't even know where i am right now [22:44] so she called me at work this morning and said 'well, i'm sorry i couldn't make it for you today', and i had to tell her 'okay' [22:45] i cant find her or the phone number or anything [22:45] i was just in the car, and she was in the kitchen [22:45] it must of been a while [22:45] i think she was off last night [22:46] that's funny that you would call me like that [22:46] then you should know that she has been off for a while [22:46] she said she was sick, and i think she said she was going to stay home and rest and it wasn't till today that i found out the truth [22:46] yeah it's a real bummer that it was a false alarm [22:46] like i said she could have possibly been sick but wasnt being honest about it [22:46] it is a big bummer that we wasted so much time on it, but it doesn't change that we found her body [22:46] yeah we know how the night went, we just dont know if she was really asleep when the phone rang [22:46] i just wish she would have just told us the truth instead of getting her feelings hurt [22:46] the real question is: why is it a phone? [22:46] that's all i got [22:46] so that's it [22:46] yeah and she's got to go find out if she's pregnant [22:46] and i guess there's no point in trying to hide the pregnancy [22:46] she said it was just a few days ago [22:46] wait what [22:46] maybe her parents are going to find it [22:46] ok [22:46] maybe if her parents find out she's pregnant [22:46] they'll just throw you out [22:46] they will [22:47] why do you think she was crying? [22:47] well, I mean, I know it's weird but [22:47] no, you're right [22:47] I mean, it was pretty strange [22:47] she just seemed, well [22:47] I don't think she could have known the guy or not [22:47] there's been plenty of reports of people getting "paedo" on the site [22:47] so it could have just been that her brain just caught on [22:47] like that one guy who was arrested last year for having a lot of chatroom porn [22:47] which is like a whole different thing [22:48] and it just happened to be in that section that she kept checking [22:48] yeah [22:48] like it's not like she has this huge fucking file of porn on her computer [22:48] so if it happens to be in one place, it's not like she's a big fucking voyeur [22:49] but still, she was watching the entire thing [22:49] yes, and that is probably why the guy stopped her [22:49] I can see your point of view [22:50] and it was also in that section that she just kept checking [22:50] yes, and I can say that she just seemed so interested in the guy that she wouldn't mind if he was watching [22:50] and that's not exactly the case with me either [22:50] but, if she's only interested in other men, then she's obviously gay [22:51] which is just something to remember [22:51] and she's so smart, but I can't see her getting on with me [22:51] she has a crush on me, but I don't even know where to start [22:52] I was at a party in NY, and someone I knew was talking to her, and they had been flirting. I didn't get a chance to respond, but I am a nice guy. She said she didn't want to talk about it any more. I am a nice guy, and I know that flirting is bad, but I also know that I like her and I think that there's a chance that it could go somewhere. I want to have a relationship with her, I don't really know where to start [22:52] you'd have to ask her yourself [22:52] but it seems like you don't have to [22:52] but if that's your only point she can't really say something else... [22:52] i think if you were to say you didn't want to have sex with her, you would lose her... [22:52] i'm not even really interested in that right now [22:53] it just seems like she wants to have sex with you [22:53] and is hoping that you'll say yes [22:53] i guess so... [22:53] but she doesn't seem to be trying to win your votes [22:53] maybe she's just trying to piss you off [22:54] and you don't have the time to argue with her [22:54] the internet is a bitch. [22:54] but i know she's just trying to be funny [22:54] and to make a point [22:54] so why can't i? [22:54] yeah [22:54] what do you mean? [22:54] jalockk: i've never seen a single one of these people [22:54] but i see them every day [22:54] and they say the same shit [22:54] we don't like the idea of them being taken out because they are not the ones we really are against [22:54] well i don't think we need to be very big to do that [22:54] but they are a part of it [22:55] the people that dont like us [22:55] the people that are behind all this [22:55] or just the people [22:55] not the people [22:55] it's the people that don't have an opinion [22:56] we should never let our ignorance define us [22:56] well we're doing it now [22:56] and it's not even funny [22:56] it's just sad [22:56] no it's a serious problem [22:56] it's not funny [22:56] and the truth is sadder [22:56] i don't understand why he hates himself so much [22:56] is it because of the death [22:56] or the lies he told [22:56] that's what im trying to figure out too [22:57] not that there is an obvious answer to why he does what he does [22:57] i think he is a pretty shitty person [22:57] the lies hurt more [22:57] i really really wish i could understand [22:58] that's why i'm here to explain the way out [22:58] if i explain it to you in words [22:58] well i don't know you [22:58] i have to explain it to you in a way that makes sense to you [22:58] in english [22:58] and that's how [22:58] this whole thing starts with a picture of a woman [22:58] holding up a phone with the words "HELLO" on the screen [22:58] it's a picture of me [22:58] It's a pic of me in a hat [22:58] and i'm in the hat [22:58] which isnt me [22:58] i'm the one with the hat [22:59] i wear a hat to hide my face [22:59] and when i say this i don't really say "i'm the hat" [22:59] i say "i'm the hat" [22:59] oh okay [22:59] ok let me get this straight [22:59] if we're talking about the "why" [22:59] what the actual, fucking, fuck [22:59] why did she do it [22:59] the "when" part I'm not clear about [22:59] i'd assume that's the part we're discussing [22:59] ok i'm getting out of this [22:59] but yeah the "what" [22:59] yeah [22:59] and it seems like the "how" [22:59] isnt really a big deal [22:59] i think it is [22:59] the fact that we all agree on what it is [22:59] and are people who say its a big deal really saying it on the op? or is it on the op, and people who say its a big deal are just assholes? [22:59] we're pretty fucking certain it's not a big deal [22:59] if you're not convinced [22:59] please say so in the thread [22:59] i'd love to hear your arguments [22:59] the op is just a big deal, it is a huge deal, we've done the math, and there is no downside [22:59] we've actually spent the last 2 days talking about it [22:59] it doesn't really have any consequences on us, as we won't do anything stupid [22:59] we'd be better off not having it in the first place [22:59] it doesn't really matter [22:59] I know I'm a bit biased but... this whole thing feels like it's been set up to be solved by trolls [22:59] not to mention that we can already see a lot of the stuff they are talking about, they just don't want to talk about it [22:59] it's not like they would go back to it and say "we got this, so why don't you shut up!" [22:59] It's frustrating to see them try and keep this open... but it's a shame to see what happens when they fail. [22:59] I love how it seems like the more they try to keep it secret, the more they are forced to keep it open [22:59] :O [23:00] well we don't know yet what they have planned for the next phase but there's a lot of work to be done [23:00] no one knows what we'll be doing now, so if we do everything right, we could actually end up with some more power [23:00] i'm not saying we'll get that, we'll have to wait and see [23:00] maybe i'm just a bit optimistic [23:00] or maybe i'm just stupid? [23:01] i dunno i don't care anymore [23:01] just wait it out [23:01] no time to waste [23:01] let them make it as easy as possible [23:01] and keep an eye on what they say next [23:01] well that could mean some kind of delay [23:01] like they are going to push it out [23:01] well, that's their prerogative [23:01] what they said a month ago is what they're saying now? [23:01] Ok, I'm gonna leave this here: http://en.wikipedia.org/wiki/Woot\_com [23:01] but I can't find the link right now. :( [23:01] it's been posted to the website of the US government [23:01] so you know it's legit [23:02] oh. Ok. [23:02] so it's legit [23:02] ok. [23:02] So, we're not really at the point of doing the whole, "we have a solution" thing, so much as a "we have a general idea" thing. [23:03] i think that's what we're going for [23:03] the problem, in my experience, is that it's hard for people to really figure out what you're talking about. I would assume that with a lot of the work that's going on there are some people who are really good at solving it. I'm not. [23:04] i mean, it is sort of in the realm of "people" [23:04] that we've been able to make progress on this, so i am assuming you have done a lot of that work? [23:04] i would have to ask someone else how they are doing it [23:05] in terms of the algorithms they use [23:05] or other tools [23:06] http://bitinfocharts.com/blocksize-and-bitcoin-future-chart/ [23:06] but i don't know how you guys did it in a way that is also practical [23:06] no problem. it's been done. [23:06] just don't expect anyone to do it for you [23:07] i'll have to ask you that one [23:07] if you have a better idea please post it here and we'll discuss it [23:07] but if we don't have a better idea then we don't know what you're talking about [23:08] it's not our fault they are doing it [23:08] they do it to us [23:08] we don't have any other solution [23:08] but they have access to your wallet [23:09] you are paying for access to it [23:09] so they are getting access [23:09] you are paying to keep their access to your wallet [23:10] I am paying to keep your access to your wallet [23:10] they are making you do it [23:10] i am paying them to keep access to my wallet [23:10] that is what i have been told to do [23:10] what i was told to do [23:10] i am also paying them for this access [23:10] I am not paying to keep access to my wallet for them [23:11] I am paying them for this access [23:11] to mine in their account for them [23:12] well, that was fun [23:12] oh, that's too bad [23:12] it's all for you [23:12] you are mining it for them [23:12] so much for that [23:12] but then you are the victim of a scam, not me [23:13] oh, ok [23:13] it's a good thing you are aware now, because that is a great way to get scammed [23:13] so what's up? [23:14] ok [23:14] we've been looking for you for a while now and we can't find you. [23:14] ok. so what's up? [23:15] the last time you were on IRC we started doing our own investigation and you didn't know where you were or how long you'd been gone [23:15] so we thought that since you weren't there anymore that it had to be a scam [23:15] which it is [23:15] http://www.youtube.com/watch?v=h0bzvq8Fx7Y [23:15] yeah. but it doesnt tell you that [23:15] you gotta ask [23:15] you got that right [23:16] alright. let me see if I can find something similar [23:16] https://www.youtube.com/watch?v=nUZpwWg1g\_s [23:16] http://www.youtube.com/watch?v=pFwX4jJYqhI [23:16] i have a different one [23:16] http://www.youtube.com/watch?v=h\_h2rK4V7ZM [23:16] it is shorter [23:16] it has less information [23:17] http://www.youtube.com/watch?v=DYpq6H2jkZg [23:17] http://www.youtube.com/watch?v=DYpq6H2jkZg [23:17] http://www.youtube.com/watch?v=DYpq6H2jkZg [23:17] http://www.youtube.com/watch?v=DYpq6H2jkZg [23:17] http://www.youtube.com/watch?v=DYpq6H2jkZg [23:17] http ://www.youtube.com [23:17] http://www.youtube.com [23:17] http://www.youtube.com [23:17] ok I have been listening [23:18] let me hear your response to the question "why are you talking on the radio?" [23:18] "The answer to that is because I was just trying to communicate with the community" [23:18] why do you think it's a good idea to try to communicate with the community? [23:18] you don't need to ask, we're going to have a drink [23:18] let me get you something to drink [23:18] i will be back later [23:18] in like 2 mins [23:18] can you hear me? [23:18] yes, I can hear you [23:18] are you a bot? [23:18] no, i am human [23:19] oh [23:19] good to know [23:19] you're just very very drunk, i guess [23:19] just go to sleep [23:20] you just have to go to sleep [23:20] and it'll be over by the morning [23:20] i'll wait [23:21] but it was only a few hours ago [23:21] and i said it wouldn't be [23:21] so i'm guessing you can't help it [23:21] so is it over? [23:21] not sure if you can help it or not, but if you have any questions or suggestions, do send them to me [23:22] but yeah, there is no immediate threat at all [23:22] but i dont know what to do at the moment, maybe i should move everything to another server [23:22] but i have the code and the rpc server [23:22] you can do that? [23:22] yeah, just let me know what you want [23:22] okay, how do i run rpc from my localhost? [23:22] just open up a terminal and run "rpcuser -i 127.0.0.1" [23:22] okay [23:22] let's go back to maint [23:22] I'm going to add another option to run the wallet (wallet.conf) as a non root user [23:22] I'm going to add rpcuser as an option, and rpcpassword as a second option [23:22] and then run as root [23:23] okay, so what do i want the output of this command to be [23:23] the output should be something like "1" [23:23] what should i put in the command? [23:23] for now, i'll just type it out [23:23] rpcuser=myuser rpcpassword=mypassword [23:23] run_in_remote.sh --port=21 --listen=127.0.0.1:2222 [23:23] you should be able to type that in [23:23] and it should go through ok. you should see something like this: [23:23] [00:11] [23:21] [00:20] [23:23] what do i do to make the next post more visible? [23:23] can someone send a screenshot of the reddit post to me? [23:23] @emmaw [23:23] i can give you my address in case you want to send something there [23:23] you're welcome [23:23] well im going to have to ask the mod team that question now [23:23] thanks for the offer, we'll think about it [23:23] :) [23:23] i'll give you the link soon, also [23:23] but please don't PM me about that :) [23:24] sure [23:24] i'll leave it with you [23:24] but i'll check it again [23:24] later [23:25] so is this the one with the red pill? [23:25] or redpilled? [23:25] redpilled [23:25] redpilled [23:25] ok [23:25] thanks [23:25] I got the link [23:25] yeah [23:25] this is a very big deal [23:25] I'm in a hurry, so I can't see the link, but what you're doing is a lot more powerful than most of what I've ever heard before [23:26] http://www.youtube.com/watch?v=Hjf7hKQ6uQg [23:26] that's a pretty long video [23:26] yeah [23:26] there's lots of cool stuff in there, too [23:26] it has a nice flow to it, too [23:26] so, you have to remember: don't focus on the structure, focus on the content [23:27] i see [23:27] not sure if thats just me though [23:27] its a good thing to have [23:27] not sure why the devs don't do it, but there are some good reasons [23:27] yeah i got your point [23:27] im happy to make it easy for you [23:27] and for other devs to do it as well [23:27] (at least a few of the devs are here to see this) [23:27] we could even get a group of devs to go talk to the press and try to have the topic in a few of the big gaming sites [23:28] this could be a great way to get the game out and to everyone else [23:28] and then we can move onto the next thing [23:28] if this is successful I think we can even get some of the smaller ones to try it [23:28] also if any of the other big ones do it this will get them in on the process
submitted by ShadowWolf525 to WeirdGeneratedStories [link] [comments]

Bitcoin Unlimited - Bitcoin Cash edition 1.4.0.0 has just been released

Download the latest Bitcoin Cash compatible release of Bitcoin Unlimited (1.4.0.0, August 17th, 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:
 
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: https://github.com/BitcoinUnlimited/BitcoinUnlimited/blob/dev/doc/release-notes/release-notes-bucash1.4.0.0.md
 
Ubuntu PPA repository for BUcash 1.4.0.0 has been updated
submitted by s1ckpig to btc [link] [comments]

Electroneum Fork 324500

Source: https://www.facebook.com/electroneum/posts/2030562537205714
Hi Everyone!
ALL ELECTRONEUM NODE OWNERS MUST UPDATE THEIR SOFTWARE BY BLOCK 324500 (approx. 36 hours from now – this is an URGENT UPDATE – PLEASE SHARE THIS INFORMATION)
We have an urgent software update below for anyone who runs a full Electroneum Node. If you don’t know what a node is , don’t worry! You won’t need to do anything.
We also have a VERY exciting update about an upcoming listing on a top 10 exchange.
How will I mine Electroneum after this update?
Instant Payment vendor API is open for BETA applicants.How can ETN change the world?
Please note that nothing in this message refers to MOBILE MINING – we are referring to the underlying blockchain miners.
Urgent Electroneum Node / RPC / Command Line Wallet Update
ALL ELECTRONEUM NODE OWNERS MUST UPDATE THEIR SOFTWARE BY BLOCK 324500 (approx. 36 hours from now – this is an URGENT UPDATE – PLEASE SHARE THIS INFORMATION)
https://github.com/electron…/electroneum/releases/…/v2.1.0.0
It’s only been a few short days since I made a video and said “our fork went well! We’re ready for 20m Users!”.
The fork was a great success, from a technical standpoint. Unfortunately, we never got back the number of GPU miners that are needed to ensure our network runs smoothly and has stable block emission. A new phenomenon has emerged where a number of users are mining Electroneum in waves. They come on and then leave after a few hours in a coordinated manner to mine ETN in a completely selfish way. We can’t blame people for maximizing their profit, but we have not built up the amount of “hashing power” that is required to make this impossible and create the stability we need in the network.
This has left us at risk. As such, we have to take urgent action to stabilise our network and protect the Electroneum community.
Coinbene Listing Electroneum & our network stability
We have formally agreed and signed contracts to be listed in July on the AWESOME, top 10, cryptocurrency exchange https://Coinbene.com & https://Coinbene.com.br
Coinbene have 1.5m active users and are a GREAT fit for Electroneum. Their primary markets are Latin America and Asia – which fits perfectly with Electroneum’s customer base. They have seen enormous growth over the last few months and have been very positive about the Electroneum Project.
Whilst this is great news, we will need much more hashing power to ensure we have network stability for our listing on this exchange, so we’ve taken the decision that we can’t wait any longer for GPU miners to return to us and we must run an urgent software update to re-introduce ASIC mining to Electroneum.
This is a very positive move for Electroneum. A great deal of Bitcoin’s trust and appeal is from the enormous hashing power and distribution of miners on the network. Bitcoin & LiteCoin have embraced ASICs and we feel that it is the right thing for Electroneum to do the same.
ASICS are becoming more prevalent, they cost considerably less to run than a GPU rig and use a fraction of the electricity. We are going to encourage more ASIC ownership and take our hashing rate up to (and beyond) the enormous levels of hashing power that we had before the May fork.
There is a further development. The first generation of hardware called an FPGA miner is arriving during 2018 and they make ANTI-ASIC capabilities a thing of the past, as they circumvent the slow delivery time of new ASICs by being re-programmable. If we are ready to embrace these rather than fight them, our network hashing power is increased further and our network stability and security is further enhanced.
Because ASICS run cooler, quieter and use a fraction of GPU rig power, they are suitable for MORE people to run in their homes. If you are interested, a search of “Cryptonight ASIC miner” in Google or Ebay will find the equipment needed to mine Electroneum. You will need to be reasonably technical to achieve this!
Having a stable network is absolutely key to both delivering mass adoption and to ensure we have a great relationship with the great exchanges that we’re already listed with, and to encourage more of the larger exchanges to see Electroneum as a coin that they want on board.
How will I mine Electroneum after this update?
If you are a mobile miner – nothing changes. If you are a GPU or ASIC miner then you’ll need to connect to an Electroneum pool but it is important to note that you will need to change your ALGORITHM. You MUST use the algorithm “Cryptonight” and NOT “Electroneum” or “CryptonightV7”. This will ensure your device works after the update. We will communicate this to all pools, but if you are a member of a mining pool – PLEASE LET THE ADMINS KNOW ABOUT THIS CRITICAL UPDATE. They must update their pool node by block 324500, which is only around 36 hours away.
Instant Payment vendor API is open for BETA applicants
Instant Cryptocurrency Payments via smart phone has always been a critical part of what Electroneum required to achieve mass market adoption. It’s never been done, but 9 short months after our ICO we are excited to announce that we have opened to the doors to vendors who would like to accept payment via Electroneum. The application is to be part of the BETA rollout of instant payment, but will operate on the live blockchain with real ETN!
If you run a business or know someone who does – why not recommend they apply to accept ETN. The Press and Marketing opportunities for the first, in any sector, to accept cryptocurrency are huge! Be part of the instant payment API BETA program by completing this form:
https://docs.google.com/…/1FAIpQLSfKTwWT7W4ltmApZO…/viewform
How can ETN change the world?
Instant payment does far more than allow people to pay for their coffee with crypto instead of their VISA card.
If you’d like to know more about Electroneum’s future I suggest you read a fantastic article that describes its coming role in the world, by fellow director Chris Gorman OBE (Officer of the British Empire – awarded by the Queen of England!): https://www.linkedin.com/…/how-cryptocurrency-enable-financ…
Electroneum has one of the largest of all cryptocurrency communities and it is made up of passionate and amazing people. With your support and world changing things we have coming out over the next few weeks, we can use this update to make our blockchain foundation secure and lead the world in mobile cryptocurrency.
I'm sure you agree that we've been through some challenging times which our team have always dealt with and learned from. The strength and support from our community and many of our goals becoming a reality combined with this blockchain update will give us the perfect foundation to deliver the Electroneum vision that we all share.
Thanks for taking the time to read this long message.
Have a great day everyone,
Richard Ells
Founder, Electroneum.com
submitted by MulatuTesh to Electroneum [link] [comments]

Install library on Archlinux

Hello Guys,

I'm new in the arch-linux world and I have a problem with method installing library c++

I have to need to install this library, this library has the dependences
  1. jsoncpp
  2. libjson-rpc-cpp
I have install this dependence but when installing the main library I have an error libjsoncpp.so not found.

I have installed the libraries with this command
  1. sudo pacman -S jsoncpp
  2. sudo aura -A libjson-rpc-cpp
Do you make any mistakes when installing the jsoncpp library?

The message error is
[[email protected] build]$ cmake .. CMake Error at cmake/FindJSONCPP.cmake:35 (MESSAGE): Could not find JSONCPP library include: JSONCPP_INCLUDE_DIRS-NOTFOUND, lib: /uslib/libjsoncpp.so Call Stack (most recent call first): src/bitcoinapi/CMakeLists.txt:1 (FIND_PACKAGE) -- Configuring incomplete, errors occurred! See also "/home/vincenzo/Github/bitcoin-api-cpp/build/CMakeFiles/CMakeOutput.log". CMake Error: Unable to open check cache file for write. /home/vincenzo/Github/bitcoin-api-cpp/build/CMakeFiles/cmake.check_cache 

Sorry for my terrible English but I'm learning
submitted by crazyjoker96 to archlinux [link] [comments]

...was I just shadow banned from /r/Bitcoin ?

I replied to theymos , regarding the bitcoin core client's RPC command: invalidateblock. I asked if this would have really allowed a node to manually fork if a block was discovered to be infected from the <0.16.3 vulnerability.
My question/reply revolved around whether or not that would do anything other than stall the node, since the getblocks message only returns a list of block hashes for the "best" chain, so the node wouldn't receive any blocks until a fork beat out the corrupted one.
It appears my comment does not show up in incognito. Curious if anyone else can see my comment or if I was shadow banned long ago...
If I was actually shadowbanned, then I'm a bit more than miffed. I'm genuinely asking about the behavior of the protocol to make sure my logic in Bitcoin Verde's implementation is correct. Cool.
EDIT: The comment chain I'm referring to: https://www.reddit.com/Bitcoin/comments/9hkoo6/new_info_escalates_importance_upgrading_to_0163/e6d4u9q/
EDIT 2: theymos : Thanks for the reply, and if I was shadow-banned, thanks for the unban. I wish you guys would reconsider your willy-nilly banning.
EDIT 3: ...okay. What is happening here? My first reply to theymos is showing up (presumably because he himself has replied), but now my 2nd reply isn't showing up? I'm either still shadowbanned and theymos is individually approving my posts, or any reply to a moderator must be approved first before being shown, or there's a massive delay between posting and being visible to others. I'd like to believe it's the lattermost scenario, but that feels naive given the subreddit's reputation.
EDIT 4: My most recent reply is now showing up. Great. I have no idea what is going on or if I'm actually shadowbanned. Regardless, I don't care anymore; I have more important things to do than investigate.
submitted by FerriestaPatronum to btc [link] [comments]

DogeCash Development Update #2

Welcome Doges to our 2nd installment of our weekly developmental updates. We have a few exciting items to talk about!
HD Wallet is being added to our core code base. This is a BIP39/44 addition for creating a mnemonic seedphrase over a traditional password for your wallet.dat! Visit our GitHub to see this and our other progress. In addition to HD Wallets, we have added xPubKey and xPrivKey commands as well. These keys are for all used and unsued addresses your wallet will hold moving forward. The commands will get you the keys in your RPC Console.
The Team is also working on bringing a light version of BitNodes, but it will feature similar to BitcoinCash’s fork of BitNodes as seen Here. Alongside BitNodes, we are looking into BitCluster. Both of these tools will bring us more information on our network size, and different statistics. Showing us who is running what versions of wallets and how the network is spread across the globe. Bringing to us also more indepth block information to be able to go through your coins easier.
Last, but surely not least is we are going to talk about SignalHub, for those of you just tuning in SignalHub is our first of many platforms in the DogeCash ecosystem. It is a non-traditional Signal Trading platform. Traders can post/sell Signals for users to purchase/subscribe from their Traders they follow. We will be supporting select coins during the beta process, and expanding it daily throughout and until we go live. As well as support for many exchanges to bring a robust amount of choices for Signals listing and purchasing. Traders should have all they need in one place and the users will have the information they need from the good Traders! So join us for the closed-beta registration and enjoy the perks of helping us put together this platform and some extra free time when its complete! Beta SignUp.
That is it for this week. Aren’t you Doges excited to see whats next?
-The DogeCash Team
submitted by DogeCash to DogeCash [link] [comments]

Bitcoin Unlimited - Bitcoin Cash edition 1.6.0.0 has just been released

Download the latest Bitcoin Cash compatible release of Bitcoin Unlimited (1.6.0.0, April 24th, 2019) from:
 
https://www.bitcoinunlimited.info/download
 
This is a major release of Bitcoin Unlimited which it is compatible with the upcoming May 2019 BCH protocol upgrade; this release is also compatible with all the already activated Bitcoin Cash network upgrades, namely:
List of notable changes and fixes contained in BUcash 1.6.0.0:
 
Release notes: https://github.com/BitcoinUnlimited/BitcoinUnlimited/blob/dev/doc/release-notes/release-notes-bucash1.6.0.md  
PS Ubuntu PPA repository is currently being updated to serve for BUcash 1.6.0.0.
submitted by s1ckpig to bitcoin_unlimited [link] [comments]

A tour of the Gridcoin wallet

Hey guys, I thought I would put together an in-depth tour of the Gridcoin wallet software for all of our recent newcomers. Here I'll be outlining all the features and functions the windows GUI wallet has to offer, along with some basic RPC command usage. I'll be using the windows wallet as an example, but both linux and macOS should be rather similar. I'll be including as many pictures as I can as embedded hyperlinks.
Edit: Note that since I originally made this there has been a UI update, so your client will be different colors but all the button locations are in the same place.
This is my first post like this, so please forgive me if this appears a little scatter-brained.
This will not cover the mining setup process for pool or solo miners.
When you launch the wallet software for the first time you should be greeted with this screen.

OVERVIEW TAB

After that prompt, you should be left sitting on the main overview tab with several fields on it.
From top to bottom:

SEND TAB

Now onto the other tabs on the left side. Currently we're on the Overview tab, lets move down to the Send tab. This tab it pretty self-explanatory, you use it if you want to send coins, but I'll go over the fields here:
  • Pay To: Enter a valid gridcoin address to send coins too. Gridcoin addresses always start with an S or and R.
  • Label: Enter a label here and it will put that address in your "address book" under that label for later use. You can leave it blank if you don't want it in your address book.
  • Message: Enter a message here if you want it attached to your transaction.
  • Amount: How many coins you want to send.
  • Add Attachment: Leave this alone, it is broken.
  • Track Coins: This doesn't do anything.

RECEIVE TAB

Now down to the Receive tab. Here you should have a single address listed. If you double click on the label field, you can edit it's label.
  • New: Generate a new address.
If you click on an address, the rest of the options should be clickable.
  • Copy: Copy the selected address to your clipboard.
  • Show QR Code: Show a scan-able QR code for the selected address.
  • Sign Message: Cryptographically sign a message using the selected address.

TRANSACTIONS TAB

The Transactions tab is pretty boring considering we have no transactions yet. But as you can see there are some sorting tools at the top for when you do have transactions listed.

ADDRESS BOOK TAB

The Address Book is where all the addresses you've labeled (that aren't yours) will show up.
  • Verify Message: Verifies a message was signed by the selected address.
The rest of the functions are similar to the functions on the Receive tab.

VOTING TAB

Onto the Voting tab. There wont be any polls because we aren't in sync yet.
  • Reload Polls: Pretty self-explanatory, I've never had to use this.
  • Load History: By default, the wallet will only display active polls. If you want to view past polls you can use this.
  • Create Poll: You can create a network-wide poll. You must have 100,000 coins as a requirement to make a poll. (Creating a poll does not consume the coins)
Here's what the Voting tab will look like once you're in sync

CONTEXT BAR

Now onto the context bar menus on the top.
Under File you have:
  • Backup Wallet/Config: This lets you backup your wallet configuration file just in case.
  • Export: You can export your Transactions tab or Address Book in CSV format.
  • Sign message: Does the same thing as on the Receive tab.
  • Verify message: Does the same thing as on the Address Book tab.
  • Exit: Close the wallet.
Under Settings you have:
  • Encrypt Wallet: Encrypts your wallet with a password. (we'll come back to this)
  • Change Passphrase: Allows you to change your encryption password.
  • Options: Opens the options menu. (We'll come back to this)
Under Community you have:
Under Advanced you have:
  • Advanced Configuration: Opens the Advanced Configuration menu. (Not so advanced if you ask me)
  • Neural Network: Allows you to view solo miners project statistics. It will be largely blank if you're not in sync yet.
  • FAQ: Don't touch this, It is broken.
  • Foundation: Don't touch this, It is broken.
  • Rebuild Block Chain: Starts the client syncing from 0. Don't worry, using this will not make you lose coins.
  • Download Blocks: Downloads the latest official snapshot, can help speed up syncing. The download progress tends to sit at 99.99% for a long time, don't worry, it's working.
Under Help you have:
  • Debug window: Opens the debug window. (We'll come back to this)
  • Diagnostics: Don't touch this, it is broken. This has since been fixed. You can use this to see if there is anything wrong with your setup.
  • About Gridcoin: Opens the About Dialog. This gives you your client version and other information.

OPTIONS

Now back to the options menu under Settings > Options.
Here we have the options menu main tab:
  • Pay transaction fee: The transaction fee that will be automatically paid when you make a transaction.
  • Reserve: You can reserve an amount so that it will always be available for spending.
  • Start Gridcoin on system login: Pretty self-explanatory
  • Detach databases at shutdown: Speeds up shutdown, but causes your blockchain file to no longer be portable.
On the Network tab:
  • Map port using UPnP: Attempts to connect to nodes through UPnP.
  • Connect through SOCKS proxy: Allows you to connect through a proxy.
The window tab is pretty self-explanatory.
The Display tab is also pretty self-explanatory, with the exception of:
  • Display coin control features (experts only!): This allows you to have a great deal of control over the coins in your wallet, check this for now and I'll explain how to use it further down. Don't forget to click "Apply".

ENCRYPTING YOUR WALLET

Now that all of that is out of the way. The first thing you'll want to do is encrypt your wallet. This prevents anybody with access to your computer from sending coins. This is something I would recommend everyone do.
Go to Settings > Encrypt Wallet and create a password. YOU CANNOT RECOVER YOUR COINS IF YOU FORGET YOUR PASSWORD.
Your wallet will close and you will have to start it up again. This time when it opens up, you should have a new button in the bottom left. Now if you want to stake you will have to unlock your wallet. Notice the "For staking only" box that is checked by default. If you want to send a beacon for solo mining or vote, you will need to uncheck this box.

GETTING IN SYNC AND ICONS

Before we continue, Let's wait until we're in sync. Depending on your internet speeds, this could take from several hours to over a day or 2. This can be sped up by using Advanced > Download Blocks, but this can still take several hours.
This is what an in-sync client should look like. Notice the green check to the right of the Receive tab. All of these icons give you information when you hover your mouse over them.
The lock
The arrow tells you if you're staking. If you aren't staking, it will tell you why you're not staking. If you are staking it will give you an estimated staking time. Staking is a very random process and this is only an estimate, not a countdown.
The connection bars tell you how many connections to the network you have.
The check tells you if you're in sync.

WHAT IS STAKING?

Now I've said "stake" about a million times so far and haven't explained it. Gridcoin is a Proof of Stake (PoS) coin.
Unlike bitcoins Proof of Work (PoW), PoS uses little system resources, so you can use those resources for scientific work. PoS works by users "Staking" with their balance. The higher the balance, the higher the chance to create, or "stake" a block. This means you need to have a positive balance in order to stake. Theoretically, you can stake with any amount over 0.0125 coins, but in practice it's recommended to have at least 2000 coins to reliably stake.
Staking is important for solo miners, because they get paid when they stake. Pool miners don't need to stake in order to get paid however. So if you want to solo mine, you'll need to buy some coins from an exchange or start in the pool first and move to solo when you have enough coins.
In addition to Research Rewards for miners, anyone who holds coins (solo miners, pool miners, and investors) gets 1.5% interest annually on top of your coins. So it can be beneficial for pool miners to stake as well.
Here is a snippet of what a research rewards transaction looks like from my personal wallet. I have a label on that address of "Payout address" as you can see here.

UTXOS AND COIN CONTROL

At this point you'll need some coins. You can use one of our faucets like this one or this one to test coin control out.
First let me explain what a UTXO is. UTXO stands for Unspent Transaction Output. Say you have an address with 0 coins in it, and someone sends you 10 coins like I've done here. Those 10 coins are added to that address in the form of a UTXO, so we have an address with one 10 coin UTXO in it.
Now we receive another 5 coins at the same address, like so. Now we have an address with one 10 coin UTXO and one 5 coin UTXO. But how do we view how our addresses are split up into different UTXOs?
Earlier we checked the "Display coin control features" box in Settings > Options > Display. Once that's checked you'll notice there's another section in the Send tab labeled "Coin Control Features". If you click the "Inputs" button, you'll get a new window. And look, there's our 2 UTXOs.
All UTXOs try to stake separately from each other, and remember that the chance a UTXO has to stake is proportional to it's size. So in this situation, my 10 coin UTXO has twice the chance to stake as my 5 coin UTXO. Now wallets, especially ones that make a lot of transactions, can get very fragmented over time. I've fragmented my wallet a little so I can show you what I'm talking about.
How do we clean this up? We can consolidate all this into one UTXO by checking all the boxes on the left and selecting OK.
Now pay attention to the fields on the top:
  • Quantity: The total amount of UTXOs we have selected.
  • Amount: The total amount of coins we have selected.
  • Fee: How much it would cost in fees to send all those UTXOs (more UTXOs = more transaction data = more fees)
  • After Fee: Amount - Fees.
  • Bytes: How large the transaction is in bytes.
  • Priority: How your client would prioritize making a transaction with this specific set of UTXOs selected had you not used coin control.
  • Low Output: If your transaction is less than 0.01 coins (I think).
  • Change: What you will get back in change.
  • custom change address: You can set the address you get your change back at, by default it will generate a new address.
So let's fill out our transaction so we end up with 1 UTXO at the end.
In "Pay To:" Just put any address in your wallet, and for the amount put what it has listed in the "After Fee" Field. Just like this.
Notice how we get no change back.
Now click "Send", we'll be prompted to enter our passphrase and we're asked if we want to pay the fee, go ahead and click "Yes".
Now if we go back to the Overview tab we get this funky icon. If you hover your mouse over it, it says "Payment to yourself", and the -0.0002 GRC is the network transaction fee.
(Ignore the first one, that was me fragmenting my wallet)
Now if we look at the Coin Control menu, we can see that we've slimmed our wallet down from 7 UTXOs to 1.
Now why would you want to use coin control?
2 Situations:
  1. UTXOs less than 0.0125 coins cannot stake. So you can combine a lot of tiny, useless UTXOs into 1 bigger one that can stake.
  2. After a UTXO stakes, it cannot stake for another 16 hours. So if you have 1 large UTXO that is big enough to stake more than once every 16 hours, you can split it into smaller UTXOs which can allow you to stake slightly more often.
  3. By default, the wallet will always generate a new address for change, which can make your wallet get very messy if you're sending lots of transactions. Keep in mind that more UTXOs = larger transactions = more fees.
Sidenote - When you stake, you will earn all research rewards owed reguardless of which UTXO staked. However, you'll earn the 1.5% interest for that UTXO. Not your whole wallet.

FORKING

A fork is when the network splits into multiple chains, with part of the network on each chain. A fork can happen when 2 blocks are staked by different clients at the same time or very close to the same time, or when your client rejects a block that should have been accepted due to a bug in the code or through some other unique circumstance.
How do I know if I'm on a fork?
Generally you can spot a fork by looking at the difficulty on your Overview tab. With current network conditions, if your difficulty is below 0.1, then you're probably on a fork.
You can confirm this by comparing your blockhash with someone elses, like a block explorer.
Go to [Help > Debug Window > Console]. This is the RPC console, we can use to do a lot of things. You can type help to get a list of commands, and you can type help [command you need help with] (without the brackets) to get information on a command. We'll be using the getblockhash [block number] command.
Type getblockhash [block number] in the console, but replace [block number] with the number listed next to the "Blocks:" field on the Overview tab.
This will spit out a crazy string of characters, this is the "blockhash" of that block.
Now head over to your favorite block explorer, I'll be using gridcoinstats. Find the block that you have the hash for, use the search bar or just find it in the list of blocks.
Now compare your hash with the one gridcoinstats gives you. Does it match?
If it matches, then you're probably good to go. If it matches but you still think you're on a fork, then you can try other block explorers, such as gridcoin.network or neuralminer.io.
If it doesn't match, then you need to try to get off that fork.
How do I get off a fork?
  1. Just wait for an hour or two. 95% of the time your client is able to recover itself from a fork given a little time.
  2. Restart the client, wait a few minutes to see if it fixes itself. If it doesn't restart again and wait. Repeat about 4 or 5 times.
  3. Find where the fork started. Using the getblockhash command, go back some blocks and compare hashes with that on a block explorer so you can narrow down what the last block you and the block explorer had in common. Then use reorganize [the last block hash you had in common]. Note that reorganize takes a blockhash, not a block number.
  4. Use Advanced > Download Blocks.
  5. If none of this works, you can take a look at social media (reddit/steemit) and see what other people are saying.

CONFIGURATION FILE

Your configuration file depends on your operation system:
  • On Windows: %appdata%\GridcoinResearch\
  • On Linux: ~/.GridcoinResearch/
  • On MacOS: /Users/USERNAME/Library/Application/Support/GridcoinResearch/
And it should look like this.
If you open up your gridcoinresearch.conf, you'll see the default one it generated. Note that if you entered your email earlier, the first line will have your email on it instead of "investor". If you decided you want to solo mine but didn't enter your email when you first started the wallet, go ahead and put your email on the first line in place of "investor". If you're a pool miner, just leave it as "investor".
Next, it's recommended that you use the addnodes on the gridcoin wiki. So our gridcoinresearch.conf will look like this.
A useful line for solo miners is PrimaryCPID=[YOUR CPID]. Sometimes your wallet can pick up on the wrong CPID so it's good to have that in there if you're solo mining.

RUNNING A LISTENING NODE

A listening node is a node that listens for blocks and transactions broadcasted from nodes and forwards them on to other nodes. For example, during the syncing process when you're getting your node running for the first time, you're downloading all the blocks from listening nodes. So running a listening node helps support the network.
Running a gridcoin listening node is simple. All you need to do is add listen=1 to your gridcoinresearch.conf and you need to forward port 32749 on your router.
If you don't know how to port forward, I'd suggest googling "How to port forward [your router manufacturer]".

QUICK LINKS

Gridcoin.us Official Website
Gridcoin.science Unofficial Website
Gridcoinstats.eu Block Explorer
NeuralMiner.io Block Explorer
Gridcoinstats.eu Faucet
Gridcoin.ch Faucet
Gridcoin Wiki
Gridcoin Github
GRCPool
Arikado Pool
And that's all I have for now!
I plan to keep this post up-to-date with changes in the client. So if anyone has any suggestions, have clarifications they want made, or maybe I got something wrong, then please feel free to leave a comment below or PM me!
submitted by Personthingman2 to gridcoin [link] [comments]

Bitcoin Unlimited - Bitcoin Cash edition 1.6.0.0 has just been released

Download the latest Bitcoin Cash compatible release of Bitcoin Unlimited (1.6.0.0, April 24th, 2019) from:
 
https://www.bitcoinunlimited.info/download
 
This is a major release of Bitcoin Unlimited which it is compatible with the upcoming May 2019 BCH protocol upgrade; this release is also compatible with all the already activated Bitcoin Cash network upgrades, namely:
List of notable changes and fixes contained in BUcash 1.6.0.0:
 
Release notes: https://github.com/BitcoinUnlimited/BitcoinUnlimited/blob/dev/doc/release-notes/release-notes-bucash1.6.0.md
 
PS Ubuntu PPA repository is currently being updated to serve for BUcash 1.6.0.0.
submitted by s1ckpig to Bitcoincash [link] [comments]

Transcript of Developer Meeting in Discord - March 29, 2019

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

Photon Networking 2 - Creating Rooms Setting up a Tezos node and bakery via command line, just copy and paste! Building Bitcoin Websites - YouTube How to Brute Force a Bitcoin Wallet with Hashcat

On the other side, bitcoin-cli looks up your rpc connection information in the bitcoin configuration file, makes an http connection to the server, encodes the method name and parameters you specify on the command line as JSON, makes a specially formed http request which includes this data, decodes the resulting JSON data from the http response [command] List commands, or get help for a command. N importprivkey <bitcoinprivkey> [label] [rescan=true] Adds a private key (as returned by dumpprivkey) to your wallet. This may take a while, as a rescan is done, looking for existing transactions. Optional [rescan] parameter added in 0.8.0. $ ./bitcoind -daemon bitcoin server starting $ ./bitcoin-cli -rpcwait help # shows the help text A list of RPC calls will be shown. $ ./bitcoin-cli getbalance 2000.00000 If you are learning the API, it is a very good idea to use the test network (run bitcoind -testnet and bitcoin-cli -testnet). JSON-RPC command (String, required): ‘add’ to add a IP/Subnet to the list, ‘remove’ to remove a IP/Subnet from the list; bantime (numeric, optional) time in seconds how long (or until when if [absolute] is set) the ip is banned (0 or empty means using the default time of 24h which can also be overwritten by the -bantime startup argument) Use bitcoin-cli help to get a list of all RPC commands. Use bitcoin-cli help <command> to get information about RPC command <command>. share | improve this answer | follow | edited Feb 22 '16 at 5:06. Felix Weis. 259 3 3 silver badges 9 9 bronze badges. answered Oct 20 '13 at 9:13.

[index] [22723] [12719] [27054] [28289] [15868] [7342] [17338] [15734] [194] [6758]

Photon Networking 2 - Creating Rooms

Skip navigation Sign in. Search Skip navigation Sign in. Search Skip navigation Bitcoin-Core: Import private key from old watch only address into non spendable wallet - Duration: 8:10. Bitcoin Daytrader 8,757 views. 8:10. Skip navigation Sign in. Search

Flag Counter