Bitcoind – Commands, RPC Protocol, Install Server

Connection string for RPC when there's no user_name and password /r/Bitcoin

Connection string for RPC when there's no user_name and password /Bitcoin submitted by BitcoinAllBot to BitcoinAll [link] [comments]

Megacoin MΣC 1.9.9.x - Release Notes - Short Overview

Megacoin MΣC 1.9.9.x - Release Notes - Short Overview

https://preview.redd.it/3ex64pfi6k251.jpg?width=1452&format=pjpg&auto=webp&s=c029b11966e1215b4bb95be70756923830c150a6

Masternodes
Megacoin MΣC 1.9.9.x brings along a masternode system for Bitcore. The collateral for one masternode is 4,200 MΣC . This allows up to 10,000 masternodes to support the network. The masternodes receive half of all generated bitcores. It is possible to setup a masternode with the minimum version 1.9.9.x or higher. A government system is included in the new core
Datacarriersize

https://preview.redd.it/jyf7ka176k251.jpg?width=1288&format=pjpg&auto=webp&s=cd6f881532ffb0b26f02bc19ca73ecb52882748a
Megacoin MΣC 1.9.9.x increase the default datacarriersize up to 220 bytes. More infos con you find here | here no 2. | here no 3.
Command fork system
Different forks can be activated remotely in the future. This way we can ensure that all critical updates are only activated once all important network participants are ready.
Wallet changes
Megacoin MΣC 1.9.9.x introduces full support for segwit in the wallet and user interfaces. A new `-addresstype` argument has been added, which supports `legacy`, `p2sh-segwit` (default), and `bech32` addresses. It controls what kind of addresses are produced by `getnewaddress`, `getaccountaddress`, and `createmultisigaddress`. A `-changetype` argument has also been added, with the same options, and by default equal to `-addresstype`, to control which kind of change is used.
A new `address_type` parameter has been added to the `getnewaddress` and `addmultisigaddress` RPCs to specify which type of address to generate.
A `change_type` argument has been added to the `fundrawtransaction` RPC to override the `-changetype` argument for specific transactions.
All segwit addresses created through `getnewaddress` or `*multisig` RPCs explicitly get their redeemscripts added to the wallet file. This means that downgrading after creating a segwit address will work, as long as the wallet file is up to date.
All segwit keys in the wallet get an implicit redeemscript added, without it being written to the file. This means recovery of an old backup will work, as long as you use new software.
All keypool keys that are seen used in transactions explicitly get their redeemscripts added to the wallet files. This means that downgrading after recovering from a backup that includes a segwit address will work
Note that some RPCs do not yet support segwit addresses. Notably, `signmessage`/`verifymessage` doesn't support segwit addresses, nor does `importmulti` at this time. Support for segwit in those RPCs will continue to be added in future versions.
P2WPKH change outputs are now used by default if any destination in the transaction is a P2WPKH or P2WSH output. This is done to ensure the change output is as indistinguishable from the other outputs as possible in either case.
BIP173 (Bech32) Address support ("mec.." addresses)

https://preview.redd.it/kzg55cg36k251.jpg?width=1288&format=pjpg&auto=webp&s=288ac36af63f4f5040ca2d20c9d8f07b78d99a5a

Full support for native segwit addresses (BIP173 / Bech32) has now been added.
This includes the ability to send to BIP173 addresses (including non-v0 ones), and generating these addresses (including as default new addresses, see above).
A checkbox has been added to the GUI to select whether a Bech32 address or P2SH-wrapped address should be generated when using segwit addresses. When launched with `-addresstype=bech32` it is checked by default. When launched with `-addresstype=legacy` it is unchecked and disabled.
HD-wallets by default
Due to a backward-incompatible change in the wallet database, wallets created with version 0.15.2 will be rejected by previous versions. Also, version 0.15.2 will only create hierarchical deterministic (HD) wallets. Note that this only applies to new wallets; wallets made with previous versions will not be upgraded to be HD.
Replace-By-Fee by default in GUI
The send screen now uses BIP125 RBF by default, regardless of `-walletrbf`.There is a checkbox to mark the transaction as final.
The RPC default remains unchanged: to use RBF, launch with `-walletrbf=1` oruse the `replaceable` argument for individual transactions.
Wallets directory configuration (`-walletdir`)
Megacoin MΣC 1.9.9.x now has more flexibility in where the wallets directory can belocated. Previously wallet database files were stored at the top level of thebitcoin data directory. The behavior is now:
For new installations (where the data directory doesn't already exist), wallets will now be stored in a new `wallets/` subdirectory inside the data directory by default.
For existing nodes (where the data directory already exists), wallets will be stored in the data directory root by default. If a `wallets/` subdirectory already exists in the data directory root, then wallets will be stored in the `wallets/` subdirectory by default.- The location of the wallets directory can be overridden by specifying a
`-walletdir=` option where `` can be an absolute path to a directory or directory symlink.
Care should be taken when choosing the wallets directory location, as if itbecomes unavailable during operation, funds may be lost.
Support for signalling pruned nodes (BIP159)


Pruned nodes can now signal BIP159's NODE_NETWORK_LIMITED using service bits, in preparation forfull BIP159 support in later versions. This would allow pruned nodes to serve the most recent blocks. However, the current change does not yet include support for connecting to these pruned peers.
GUI changes
We have added a new Walletdesign. The option to reuse a previous address has now been removed. This was justified by the need to "resend" an invoice, but now that we have the request history, that need should be gone.- Support for searching by TXID has been added, rather than just address and label.- A "Use available balance" option has been added to the send coins dialog, to add the remaining available wallet balance to a transaction output.- A toggle for unblinding the password fields on the password dialog has been added
Security
We change the coinbase maturity via command fork from 100 to 576 blocks. Also we have pumb the default the protoversion to 70006. It is possible later to disconnect the old version via command fork.
Hashalgorythm
Megacoin MΣC 1.9.9.x supports a completely new hashalgo "Mega_MEC".
Sources
Bitcoin Core, Dash Core, FXTC Core, LTC Core, PIVX Core, Bitcoin Cash Core, Bitcore BTX Odarhom
submitted by limxdev to megacoinmec [link] [comments]

Odarhom - Release Notes - Short Overview - First Draft

Odarhom - Release Notes - Short Overview - First Draft

Odarhom
Masternodes
Odarhom brings along a masternode system for Bitcore. The collateral for one masternode is 2,100 BTX. This allows up to 10,000 masternodes to support the network. The masternodes receive half of all generated bitcores. It is possible to setup a masternode with the minimum version 0.90.8.x or higher. A government system is included in the new core and can be activated later, if necessary.
Datacarriersize

https://preview.redd.it/csrmknzl58q41.jpg?width=1267&format=pjpg&auto=webp&s=85c59b3e5753009f397505c3000e6d70892188b7
Odarhom increase the default datacarriersize up to 220 bytes. More infos con you find here | here no 2. | here no 3.
Command fork system
Different forks can be activated remotely in the future. This way we can ensure that all critical updates are only activated once all important network participants are ready.
Wallet changes
Odarhom introduces full support for segwit in the wallet and user interfaces. A new `-addresstype` argument has been added, which supports `legacy`, `p2sh-segwit` (default), and `bech32` addresses. It controls what kind of addresses are produced by `getnewaddress`, `getaccountaddress`, and `createmultisigaddress`. A `-changetype` argument has also been added, with the same options, and by default equal to `-addresstype`, to control which kind of change is used.
A new `address_type` parameter has been added to the `getnewaddress` and `addmultisigaddress` RPCs to specify which type of address to generate.
A `change_type` argument has been added to the `fundrawtransaction` RPC to override the `-changetype` argument for specific transactions.
All segwit addresses created through `getnewaddress` or `*multisig` RPCs explicitly get their redeemscripts added to the wallet file. This means that downgrading after creating a segwit address will work, as long as the wallet file is up to date.
All segwit keys in the wallet get an implicit redeemscript added, without it being written to the file. This means recovery of an old backup will work, as long as you use new software.
All keypool keys that are seen used in transactions explicitly get their redeemscripts added to the wallet files. This means that downgrading after recovering from a backup that includes a segwit address will work
Note that some RPCs do not yet support segwit addresses. Notably, `signmessage`/`verifymessage` doesn't support segwit addresses, nor does `importmulti` at this time. Support for segwit in those RPCs will continue to be added in future versions.
P2WPKH change outputs are now used by default if any destination in the transaction is a P2WPKH or P2WSH output. This is done to ensure the change output is as indistinguishable from the other outputs as possible in either case.
BIP173 (Bech32) Address support ("btx..." addresses)

https://preview.redd.it/q0c26p3fx7q41.jpg?width=1278&format=pjpg&auto=webp&s=bd2b8c5d583dca703caae940aa44e01a365f080c
Full support for native segwit addresses (BIP173 / Bech32) has now been added.
This includes the ability to send to BIP173 addresses (including non-v0 ones), and generating these addresses (including as default new addresses, see above).
A checkbox has been added to the GUI to select whether a Bech32 address or P2SH-wrapped address should be generated when using segwit addresses. When launched with `-addresstype=bech32` it is checked by default. When launched with `-addresstype=legacy` it is unchecked and disabled.
HD-wallets by default
Due to a backward-incompatible change in the wallet database, wallets created with version 0.15.2 will be rejected by previous versions. Also, version 0.15.2 will only create hierarchical deterministic (HD) wallets. Note that this only applies to new wallets; wallets made with previous versions will not be upgraded to be HD.
Replace-By-Fee by default in GUI
The send screen now uses BIP125 RBF by default, regardless of `-walletrbf`.There is a checkbox to mark the transaction as final.
The RPC default remains unchanged: to use RBF, launch with `-walletrbf=1` oruse the `replaceable` argument for individual transactions.
Wallets directory configuration (`-walletdir`)
Odarhom now has more flexibility in where the wallets directory can belocated. Previously wallet database files were stored at the top level of thebitcoin data directory. The behavior is now:
For new installations (where the data directory doesn't already exist), wallets will now be stored in a new `wallets/` subdirectory inside the data directory by default.
For existing nodes (where the data directory already exists), wallets will be stored in the data directory root by default. If a `wallets/` subdirectory already exists in the data directory root, then wallets will be stored in the `wallets/` subdirectory by default.- The location of the wallets directory can be overridden by specifying a
`-walletdir=` option where `` can be an absolute path to a directory or directory symlink.
Care should be taken when choosing the wallets directory location, as if itbecomes unavailable during operation, funds may be lost.
Support for signalling pruned nodes (BIP159)

https://preview.redd.it/fctdedmwx7q41.jpg?width=1283&format=pjpg&auto=webp&s=20dafb6385f46a072f68d49fd0e9a294341be684
Pruned nodes can now signal BIP159's NODE_NETWORK_LIMITED using service bits, in preparation forfull BIP159 support in later versions. This would allow pruned nodes to serve the most recent blocks. However, the current change does not yet include support for connecting to these pruned peers.
GUI changes
We have added a new Walletdesign. The option to reuse a previous address has now been removed. This was justified by the need to "resend" an invoice, but now that we have the request history, that need should be gone.- Support for searching by TXID has been added, rather than just address and label.- A "Use available balance" option has been added to the send coins dialog, to add the remaining available wallet balance to a transaction output.- A toggle for unblinding the password fields on the password dialog has been added
Security
We change the coinbase maturity via command fork from 100 to 576 blocks. Also we have pumb the default the protoversion to 80004. It is possible later to disconnect the old version via command fork.
Hashalgorythm
Odarhom supports already lots of Hashalgorythms so can we later with an update new Hashalgorythms for mining. A final decision will be agreed with the community. Odarhom can work with timetravel10, scrypt, nist5, lyra2z, x11, x16r.
Sources
Bitcoin Core, Dash Core, FXTC Core, LTC Core, PIVX Core, Bitcoin Cash Core
submitted by limxdev to bitcore_btx [link] [comments]

PiNode-XMR (Single board computer Plug and Play Full Monero Node) Free image download and updated to v2.12.19. **Lots of new features**

PiNode-XMR (Single board computer Plug and Play Full Monero Node) Free image download and updated to v2.12.19. **Lots of new features**


https://preview.redd.it/f81i3qsnr6941.jpg?width=740&format=pjpg&auto=webp&s=da729d5a37c1be43832d7cf2ccdce6ccc4c4d637

Main project page with manual and screenshots https://github.com/shermand100/pinode-xmr
Download PiNode-XMR_v2.12.19_m0.15.0.1.img -Hosted on Google drive - 6.45GB
SHA256 Hash: 0EE90EEC65F430DC89FB3236474AA576BA0AFFFF4005B044FFE40D4A47B148F0
Hardware: Raspberry Pi 3/4 including B and + models
New Features:
  • Onion Monero Blockchain Explorer by mWo12 included.
  • Auto loading menu for Monero updates, and script that auto detects, formats and mounts attached USB drives. Labels drive for simple detection by future versions of PiNode-XMR so the blockchain is maintained between versions.
  • Public node - RPC_payments ready. Receive payment* for running a node (more info here) Pending monero/pull/6260 ( context of issue monero/issues/3083 )
All features:
  • 4 Node modes (click to start)
    • Private Node
    • tor bridging Node - routes your transactions through the tor network
    • Public Node - Using new RPC payment feature* - soon
    • Private Node - with mining (For education/experiment only)
  • Simple control with Web-UI
    • View Monero node and hardware status
    • Control bandwidth, connection limits and RPC port
    • Transaction pool and summary viewer
    • View connected peer info
    • Monerod log file view page
  • Easy setup menu for config of passwords, USB storage, Update and optional dynamic DNS.
  • All the benefits of running on a Pi, silent/fanless, low power (approx 15w) for 24/7 node, low cost.
  • Headless (No need for extra monitor,keyboard,etc) and connect via Ethernet or WiFi**
Background:
I've been making nodes for other coins for a few years to learn about some crypto basics. It got a bit of interest for I have a site https://PiNode.co.uk but recently far more advanced projects have come on the scene (such as RaspiBlitz for Bitcoin) which was so far superior there was no sense pursuing it . However there are benefits for Monero users running their own node and we didn't have that quality of plug and play node. So I've been giving it a go and this is the result.
The Future of PiNode-XMR:
First of all project needs feedback to continue, I don't know what to develop and introduce unless people say what they don't like, do like or want.
Second, it'd be great if anyone else in the Monero community would like to get involved, we have a great group and I'm sure there is an aspect of this project someone takes an interest in. Please get in touch. Like if there are any budding website designers in our midst the UI is the last module of this project that isn't open source, it's from a template and I've put it together best I can but...throwing that out there :) I'd be nice if the monero community could completely own this project, completely open source.
Finally, I know that now there is more choice on the single board computer market and although the Raspberry Pi is popular it may not be the best hardware choice. So the next plan is to rather than make disk images that are hardware specific, to instead make scripts that are based on an OS ( probably Debian ). This way this project can be built by anyone using a single command onto Pine64, Odroid, Bananapi or any old laptop/pc with Debian for thier full node.
Thanks for taking an interest and readingDan
The "Advanced Settings" page from the UI for a bit of colour after all that text:

https://preview.redd.it/4pqg5mcqr6941.png?width=1340&format=png&auto=webp&s=aa1f9ee176746ea064c8e8573ba04ee864ab5bc3
Edit: Added download link to this page too. Corrected image layout.
Edit2: Added hash of image. And note it's also possible to flash the image directly onto a USB drive with a program like Rufus and not insert a MicroSD at all. You'll need to then manually expand that partition to the size of the drive, but may be useful to know.
submitted by shermand100 to Monero [link] [comments]

Groestlcoin 6th Anniversary Release

Introduction

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

UPDATED - Groestlcoin Core 2.18.2

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

How to Upgrade?

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

Other Linux

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

Download

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

Source

ALL NEW - Groestlcoin Moonshine iOS/Android Wallet

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

Features

Download

iOS
Android

Source

ALL NEW! – HODL GRS Android Wallet

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

Features

Download

Main Release (Main Net)
Testnet Release

Source

ALL NEW! – GroestlcoinSeed Savior

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

Features

Live Version (Not Recommended)

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

Download

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

Source

ALL NEW! – Vanity Search Vanity Address Generator

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

Features

Usage

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

Download

Source

ALL NEW! – Groestlcoin EasyVanity 2020

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

Features

Download

Source

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

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

Features

Remastered Improvements

Download

Source

ALL NEW! – BIP39 Key Tool

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

Features

Download

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

Source

ALL NEW! – Electrum Personal Server

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

Features

Download

Windows
Linux / OSX (Instructions)

Source

UPDATED – Android Wallet 7.38.1 - Main Net + Test Net

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

Changes

Download

Main Net
Main Net (FDroid)
Test Net

Source

UPDATED – Groestlcoin Sentinel 3.5.06 (Android)

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

Changes

Download

Source

UPDATED – P2Pool Test Net

Changes

Download

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

Source

submitted by Yokomoko_Saleen to groestlcoin [link] [comments]

Need help with a Bitcoin Node, can't get more than 8 connections (ports already forwarded)

I've spent two days trying to figure out how to get more than 8 connections, UPNP on, UPNP off, ports open, I can't seem to get more than 8 connections

Should I put something specific in the bitcoin.conf? what should I do?

EDIT: Not sure why, but setting the port via -port=8333 seemed to fix the issue, thanks everybody!
submitted by RazerPSN to Bitcoin [link] [comments]

How can I get this script to work for Litecoin 0.8.7.5?

What would I need to do to get this script to work for Litecoin 0.8.7.5? https://github.com/litecoin-project/litecoin/releases/tag/v0.8.7.5
 class Bitcoin { // Configuration options private $username; private $password; private $proto; private $host; private $port; private $url; private $CACertificate; // Information and debugging public $status; public $error; public $raw_response; public $response; private $id = 0; /** * @param string $username * @param string $password * @param string $host * @param int $port * @param string $proto * @param string $url */ function __construct($username, $password, $host = 'localhost', $port = 8332, $url = null) { $this->username = $username; $this->password = $password; $this->host = $host; $this->port = $port; $this->url = $url; // Set some defaults $this->proto = $host == 'localhost' ? 'http':'https'; $this->CACertificate = null; } /** * @param string|null $certificate */ function setSSL($certificate = null) { $this->proto = 'https'; // force HTTPS $this->CACertificate = $certificate; } function __call($method, $params) { $this->status = null; $this->error = null; $this->raw_response = null; $this->response = null; // If no parameters are passed, this will be an empty array $params = array_values($params); // The ID should be unique for each call $this->id++; // Build the request, it's ok that params might have any empty array $request = json_encode(array( 'method' => $method, 'params' => $params, 'id' => $this->id )); // Build the cURL session $curl = curl_init("{$this->proto}://{$this->username}:{$this->password}@{$this->host}:{$this->port}/{$this->url}"); $options = array( CURLOPT_RETURNTRANSFER => TRUE, CURLOPT_FOLLOWLOCATION => TRUE, CURLOPT_MAXREDIRS => 10, CURLOPT_HTTPHEADER => array('Content-type: application/json'), CURLOPT_POST => TRUE, CURLOPT_POSTFIELDS => $request ); if ($this->proto == 'https') { // If the CA Certificate was specified we change CURL to look for it if ($this->CACertificate != null) { $options[CURLOPT_CAINFO] = $this->CACertificate; $options[CURLOPT_CAPATH] = DIRNAME($this->CACertificate); } else { // If not we need to assume the SSL cannot be verified so we set this flag to FALSE to allow the connection $options[CURLOPT_SSL_VERIFYPEER] = FALSE; } } curl_setopt_array($curl, $options); // Execute the request and decode to an array $this->raw_response = curl_exec($curl); $this->response = json_decode($this->raw_response, TRUE); //error_log('this->response: '. print_r($this->response,true)); // If the status is not 200, something is wrong $this->status = curl_getinfo($curl, CURLINFO_HTTP_CODE); // If there was no error, this will be an empty string $curl_error = curl_error($curl); curl_close($curl); if (!empty($curl_error)) { $this->error = $curl_error; } if ($this->response['error']) { // If bitcoind returned an error, put that in $this->error $this->error = $this->response['error']['message']; } elseif ($this->status != 200) { // If bitcoind didn't return a nice error message, we need to make our own switch ($this->status) { case 400: $this->error = 'HTTP_BAD_REQUEST'; break; case 401: $this->error = 'HTTP_UNAUTHORIZED'; break; case 403: $this->error = 'HTTP_FORBIDDEN'; break; case 404: $this->error = 'HTTP_NOT_FOUND'; break; } } if ($this->error) { return FALSE; } return $this->response['result']; } } /* Address History Interface Class */ class AddressHistory { public $address = null; public $n_tx = 0; public $total_sent = 0; public $total_received = 0; public $balance = 0; public $final_balance = 0; public $txns = array(); public function __construct($txn=null) { if(! is_array($txn)) return null; if(array_key_exists('address', $txn)) $this->address = $txn['address']; if(array_key_exists('n_tx', $txn)) $this->n_tx = $txn['n_tx']; if(array_key_exists('total_sent', $txn)) $this->total_sent = $txn['total_sent']; if(array_key_exists('total_received', $txn))$this->total_received = $txn['total_received']; if(array_key_exists('balance', $txn)) $this->balance = $txn['balance']; if(array_key_exists('final_balance', $txn)) $this->final_balance = $txn['final_balance']; if(is_array($txn['txns'])) { foreach($txn['txns'] as $key => $this_txn) { $new_txn = array( 'hash' => $this_txn['hash'], 'block_height' => $this_txn['block_height'], 'value' => $this_txn['value'], 'spent' => $this_txn['spent'], 'spent_by' => $this_txn['spent_by'], 'confirmations'=> $this_txn['confirmations'] ); $this->txns[$key] = new TransRef($new_txn); } } else { $this->txns = null; } return $this; } } /* Transaction Reference Interface Class */ class TransRef { public $hash; public $block_height; public $value; public $spent; public $spent_by; public $confirmations; public function __construct($txnref=null) { if(! is_array($txnref)) return null; if(array_key_exists('hash', $txnref)) $this->hash = $txnref['hash']; if(array_key_exists('block_height', $txnref)) $this->block_height = $txnref['block_height']; if(array_key_exists('value', $txnref)) $this->value = $txnref['value']; if(array_key_exists('spent', $txnref)) $this->spent = $txnref['spent']; if(array_key_exists('spent_by', $txnref)) $this->spent_by = $txnref['spent_by']; if(array_key_exists('confirmations', $txnref)) $this->confirmations = $txnref['confirmations']; return $this; } } /* CoindRPC - JsonRPC Class to talk to bitcoind */ class CoindRPC extends Bitcoin { public function __construct() { return parent::__construct(WN_RPC_USER, WN_RPC_PASS, WN_RPC_HOST, WN_RPC_PORT); } public function __call($method, $params) { return parent::__call($method, $params); } public function get_address_balance($address, $confirmations=0) { try { $address_info = $this->validateaddress($address); if($address_info['isvalid'] == 1 && $address_info['ismine'] == 1) { $balance = $this->getreceivedbyaddress($address, $confirmations); } if($balance != '') { return floatval($balance); } else { return 0; } } catch (Exception $e) { error_log('error: '. print_r($e->getMessage(),true)); error_log('['.__LINE__.'] : '.__FILE__); } } public function get_address_history($address) { try { $address_info = $this->validateaddress($address); if($address_info['isvalid'] == 1 && $address_info['ismine'] == 1) { //- if only listening to one BTC account //$history = $this->listtransactions(WN_RPC_ACCT); $history = $this->listtransactions(); $txns = array(); $final_balance = $balance = 0; foreach($history as $txn) { if($txn['address'] != $address) continue; $n_tx = $total_received = $total_sent = 0; $n_tx = intval($addr_hist['n_tx']) + 1; switch($txn['category']) { case('receive'): $total_received = $addr_hist['total_received'] += $txn['amount']; $balance = $balance + $txn['amount']; //- can we trust final balance here? do we need more history $final_balance = $final_balance + $txn['amount']; break; case('send'): $total_sent = $addr_hist['total_sent'] += $txn['amount']; $balance = $balance + $txn['amount']; //- can we trust final balance here? do we need more history $final_balance = $final_balance + $txn['amount']; break; } $txns[] = array( 'hash' => $txn['txid'], 'value' => $txn['amount'], 'spent' => $txn['spent'], 'spent_by' => $txn['spent_by'], 'confirmations' => $txn['confirmations'], ); } $addr_hist = array( 'address' => $address, 'n_tx' => $n_tx, 'total_sent' => $total_sent, 'total_received' => $total_received, 'balance' => $balance, 'final_balance' => $final_balance, 'txns' => $txns ); $addr_hist = new AddressHistory($addr_hist); } else { $addr_hist = false; error_log('Address invalid: '.$address); error_log('['.__LINE__.'] : '.__FILE__); } return $addr_hist; } catch (Exception $e) { error_log('error: '. print_r($e->getMessage(),true)); error_log('['.__LINE__.'] : '.__FILE__); } } public function get_transaction($hash) { try { return $this->gettransaction($hash); } catch (Exception $e) { error_log('error: '. print_r($e->getMessage(),true)); error_log('['.__LINE__.'] : '.__FILE__); } } } /* Helper class */ class Helper { public static $api = null; public static $db = null; public function __construct($db, $api) { Helper::$api = $api; Helper::$db = $db; } public static function walletnotify_email($txnhead) { //- bitcoind calls walletnotify on 0 confirmations and 1. //- We only want email to go out on the first call. Otherwise //- if we want only one 1 confrime, change this to //- confirmations == 0) return; if($txnhead['confirmations'] > 0) return; $tmpl = file_get_contents('email.notify.tmpl.html'); foreach($txnhead as $key => $val) { $map['{'.$key.'}'] = $val; } $map['{timestamp}'] = date('Y-m-d H:i:s', WN_GLOBAL_TIMESTAMP); $map['{hostname}'] = php_uname('n'); $html = str_replace(array_keys($map), array_values($map), $tmpl); $txid_short = substr($txnhead['txid'], 0, 4).' .. '.substr($txnhead['txid'], -4); $msg = "=WNotify=". "\ntxid: ".$txid_short. "\nAmt : ".$txnhead['amount']. "\nCmnt: ".$txnhead['comment']. "\nAcct: ".$txnhead['account']. "\nConf: ".$txnhead['confirmations']. "\nCat : ".$txnhead['category']. "\nAddr: ".$txnhead['address']. ""; //- send to carrier's email to SMS gateway if configured if(defined('WN_SMS_ADMIN') && filter_var(WN_SMS_ADMIN, FILTER_VALIDATE_EMAIL)) { Helper::send_email_sms($msg, WN_SMS_ADMIN); } return Helper::send_email($html, 'WN:WalletNotify', WN_EMAIL_ADMIN);; } public static function send_email($msg, $subj, $to) { $headers = 'From: '.WN_EMAIL_FROM."\r\n"; $headers .= "MIME-Version: 1.0\r\n"; $headers .= "Content-Type: text/html; charset=ISO-8859-1\r\n"; if(trim($msg) == '') return false; return mail($to, $subj, $msg, $headers); } public static function send_email_sms($msg, $to) { if(trim($msg) == '') return false; if($to == '') return false; $headers = 'From: '.WN_EMAIL_FROM."\r\n"; return mail($to, null, $msg."\n.", $headers); } } 
submitted by Mjjjokes to cryptodevs [link] [comments]

Dosen't inizialize propriety inside the class with the constructor compiling error

Hello guys,
I'm a java programmer and I'm studying C++ with my personal project I want to create a Singleton pattern that contains the proprieties, but when go to initialize the propriety inside the private constructor no-arg I have a compiling error with, it is this
[ 5%] Building CXX object CMakeFiles/SpyCBlockRPC.dicommands/DecodeScriptCommand.cpp.o [ 11%] Building CXX object CMakeFiles/SpyCBlockRPC.diClientBitcoinSingleton.cpp.o /home/vincenzo/Github/SpyCBlockRPC/ClientBitcoinSingleton.cpp: In constructor ‘spyCBlockRPC::ClientBitcoinSingleton::ClientBitcoinSingleton()’: /home/vincenzo/Github/SpyCBlockRPC/ClientBitcoinSingleton.cpp:9:62: error: no matching function for call to ‘BitcoinAPI::BitcoinAPI()’ spyCBlockRPC::ClientBitcoinSingleton::ClientBitcoinSingleton() ^ In file included from /home/vincenzo/Github/SpyCBlockRPC/ClientBitcoinSingleton.h:7:0, from /home/vincenzo/Github/SpyCBlockRPC/ClientBitcoinSingleton.cpp:3: /uslocal/include/bitcoinapi/bitcoinapi.h:28:5: note: candidate: BitcoinAPI::BitcoinAPI(const string&, const string&, const string&, int, int) BitcoinAPI(const std::string& user, const std::string& password, const std::string& host, int port, int httpTimeout = 50000); ^~~~~~~~~~ /uslocal/include/bitcoinapi/bitcoinapi.h:28:5: note: candidate expects 5 arguments, 0 provided /uslocal/include/bitcoinapi/bitcoinapi.h:19:7: note: candidate: constexpr BitcoinAPI::BitcoinAPI(const BitcoinAPI&) class BitcoinAPI ^~~~~~~~~~ /uslocal/include/bitcoinapi/bitcoinapi.h:19:7: note: candidate expects 1 argument, 0 provided 
This is my file ClientBitcoinSingleton.h

namespace spyCBlockRPC { class ClientBitcoinSingleton { public: static ClientBitcoinSingleton& getInstance() { static ClientBitcoinSingleton SINGLETON; return SINGLETON; } BitcoinAPI getBitcoinApi() const; private: ClientBitcoinSingleton(); //BitcoinAPI bitcoinApi{"", "", "", 8332}; //TODO chanhe this resolve the problem, I don't want inizialize it with this code BitcoinAPI bitcoinApi; } 
This is my file ClientBitcoinSingleton.cpp
#include  #include "ClientBitcoinSingleton.h" using namespace std; using namespace cppproperties; using namespace spyCBlockRPC; spyCBlockRPC::ClientBitcoinSingleton::ClientBitcoinSingleton() { string user =""; string pass = ""; string ip =""; int port = 8080; this->dirLogTest = config.GetProperty(DIR_LOG_TEST); this->dirDatatest = config.GetProperty(DIR_DATA_TEST); bitcoinApi = BitcoinAPI{user, pass, ip, port}; } 
I'm not understanding the error, how I want to write this code with no one error?

Thanks so much for your help
submitted by crazyjoker96 to cpp_questions [link] [comments]

How do I use my bitcoin core node to validate transactions against BRD, HODL, Samourai or other mobile wallets???

I have my bitcoin core node setup. I use electrum personal server and can connect electrum to my own core node just fine. However, all of these mobile wallets that allow you to "switch to manual mode" and use your own bitcoin core node dont seem to work. Some allow you to put in your RPC Username/Password and others just allow you to put in an IP and a Port. I am obviously connecting via my own local LAN between my phone and the core node. I have server=1 set in my config and I have an RPC usepassword/port setup as well. What else needs to be done here or does anyone have any tips/tricks to get this to work? Thanks.
submitted by linkd22 to Bitcoin [link] [comments]

Top 10 of The Biggest Cryptocurrency Hacks and Scams Ever

If you have been around the cryptocurrency industry long enough, you will know that one of the biggest risks faced by users is the loss of funds through hacks on cryptocurrency wallets and exchanges.
Online exchanges are prime targets for hackers and thieves on the internet. This is mainly because of the amount of funds that are kept on these platforms. For hackers that have succeeded in stealing funds from such platforms, the amounts are usually huge.
As much as individual users try to play their roles in securing their accounts by using personal passwords, PINs and codes, there is a higher layer of security that lies in the hands of the platform providers. Once this is breached, the individual security efforts become irrelevant.
Over the years, exchanges and wallets appear to have improved in terms of security as the frequency of hacks and platform breaches have reduced. What used to be a common occurrence in the industry has become a rare development, with hacks now few and far between.
Let’s take a look at the top 10 of the biggest cryptocurrency hacks and scams ever.

10. Bitcoin Gold ($18 Million)

In May 2018, the theoretical 51% attack possibility was proven in a heist that saw a breach in Bitcoin Gold which cost the protocol $18 million.
In this heist, hackers used 51% raw computing power to seize control of the network and carry out their ulterior plans effectively. Ciphertrace and other security outfits in the ecosystem believe that the algorithm weaknesses in Bitcoin Gold’s Proof of Work (PoW) transaction verification may have enabled the success of the theft.

9. Geth ($20 Million)

In June 2018, the Ethereum client Geth was hacked and ETH worth $20 million was stolen. This incidence was reported by blockchain security firm, Cyphertrace. During the hack, JSON-RPC port 8545 was exploited. This is the port that initiates ETH send transactions.
All the ETH wallets that were affected by this breach was drained by the thieves, accumulating to the quoted $20 million equivalence based on the price of ETH at that time.

8. Bancor ($23.5 Million)

In July 2018, about one month after the Geth incident, decentralized cryptocurrency exchange, Bancor was hacked and $23.5 million worth of crypto stolen. This particular event raised some eyebrows in the cryptocurrency industry, redefining the general opinion of decentralized exchanges being prone to hacking.
The process involved the exploitation of a security flaw in a wallet that was used to update some of the smart contracts on the exchange. Bancor, which was one of the most successful ICOs of 2017, raising $153 million during its token sale, was forced to shut down after the hack.

7. Coinrail ($40 Million)

Coinrail was hacked in June 2018, and $40 million was stolen from the exchange. The South Korean exchange which ranked among the top 100 exchanges by volume, suspended its services shortly after the hack.
According to sources from the exchange, the tokens that were stolen included NPXS tokens from the Pundi X project, ATC from Aston and the NPER project’s NPER token.
  1. Binance ($40.7 Million)
Binance exchange was hacked in May 2019 and 7,000 Bitcoins were stolen from the platform. The value of the Bitcoins stolen at the time was about $40.7 million.
To achieve their aim, hackers were able to steal API keys, two-factor codes and some other key information to access the wallets. According to the exchange, the incident impacted only about 2% of its total Bitcoin holdings as all other wallets are secure.
Affected wallets were promised a refund through the exchange’s Secure Asset Fund for Users (SAFU) arrangement. This is a policy that the exchange uses to prepare for rainy days. A portion of fees charged on the exchange is set aside in order to ensure that platform users do not bear the brunt during occurrences such as this.

5. Zaif ($60 Million)

Japan-based cryptocurrency exchange Zaif was hacked in September 2018 and $60 million was stolen in the process. The theft was possible after hackers gained authorised access into the exchanges hot wallets, making away with huge amounts of Bitcoin, Bitcoin Cash, and MonaCoin.
The exchange’s asset reserve could not cover the loss, therefore it reached an agreement with a Japan-listed firm called Fisco to receive a $44.5 million investment in exchange for a major share of ownership.

4. Bitfinex ($77 Million)

The Bitfinex hack of August 2016 was a popular event that rocked the entire cryptocurrency industry. The hack occurred at a time when cryptocurrencies appeared to be shifting gears in terms of awareness and development. As a matter of fact, the aftermath of the event saw the Bitcoin price drop by 20%.
After the hack, Bitfinex issued cryptographic tokens to its users that were affected by the hack, all of which the exchange announced to have bought back by April 2017.

3. BitGrail ($187 Million)

$187 million worth of Nano tokens were stolen from BitGrail in February 2018. The reported theft was announced weeks after the unauthorized transfer was initiated. This information was from evidence retrieved from the Nano blockchain explorer by skeptics.
While BitGrail recognized the concerns of it users, it however stated that it is impossible for it to refund the stolen amount.

2. Mt. Gox ($460 Million)

The Mt. Gox scandal remains one of the biggest stains on the cryptocurrency industry. In February 2014, Mt. Gox was hacked and as much as $460 million was stolen from the exchange. In the wake of this, the exchange’s CEO, Mark Karpeles issued a statement that accepted responsibility on behalf of his company.
“We had weaknesses in our system, and our bitcoins vanished. We’ve caused trouble and inconvenience to many people, and I feel deeply sorry for what has happened, “ he said.
At the time, Mt. Gox was the world’s largest Bitcoin exchange that looked impressive from the outside, but many who claimed to know about the internal workings accused the company of a messy combination of poor management, neglect, and raw inexperience.
The size of this event left a huge dent on the reputation of Bitcoin and the crypto industry at large. It took a long time before the market picked up again, and for users to regain confidence in the industry. The exchange has since gone down and ceased to exist.

1. Coincheck ($500 Million)

The biggest theft in the history of the cryptocurrency industry happened in January 2018, when Japan-based cryptocurrency exchange, Coincheck was hacked. A total of NEM tokens worth $500 million were stolen in the process.
A statement from the exchange accepted the blame and took responsibility for the breach. According to reports, rather than storing its customers’ assets in offline wallets, the assets were stored in hot wallets that were connected to the internet. Coincheck also reportedly failed to protect the wallets with standard multi-signature security protocols.
Having traced the destination of the stolen funds, NEM developers created a tracking tool that would allow exchanges to automatically reject stolen funds.

Conclusion

Hacks and massive theft of cryptocurrencies have contributed to the setback experienced by the technology. Each of the events takes a hit on the confidence of investors and willing participants who may not be sure of how the affected exchanges will handle the situation.
The industry is however learning from past experiences, as the frequency of such hacks have reduced, while in some cases, modalities are being put in place to ensure that end users do not bear the brunt of such events, just like the case of Binance.
The NEM developers’ response to the Coincheck hack has a way of rendering stolen funds unspendable, as long as other members of the community comply. However, no one knows how long this will last, and if the hackers will be able to nullify the traceability of the stolen coins yet.
The action by the developers will discourage hackers and thieves, but is yet to restore value to the end users whose funds have been stolen.
For the industry to grow as it should and become stable, security of funds need to be established. Exchanges and developers are continuously making efforts to ensure that funds and transactions within the industry remain safe at all times.
http://bitcoinadvisor.info/top-10-of-the-biggest-cryptocurrency-hacks-and-scams-eve?fbclid=IwAR1aKdbjF1HQpFQq3jH6PQptxt7mhXHJWsABPnlN5ZEjmq07ByMEYWvVezM
submitted by OliAustin101 to TopBottomCrypto [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]

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]

Lightning node on Windows - testing, get not connected

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

Eclair: Cannot create my first channel. Usually get insufficient funds error

Hello,
I decided to try to help out the lightning network by setting up an Eclair node. I followed the guide from Ivan on Tech. I set up the rpc user and password and made sure by bitcoin core 0.17 is fully synced and loaded with 0.004 BTC. At the time of this writing it has 66 confirmations.

I went to 1ML to get some nodes and tried about 20 of them. They all failed. Usually get an error about insufficient funds (code -4).

What am I doing wrong? One thing I noticed is that on the bottom of the eclair window it says total 0.0000000 BTC. Does this mean it somehow doesn't see the BTC in core?
submitted by Coldinthenorth to lightningnetwork [link] [comments]

Soo after almost 3 months of setting up I have my own LN full node running on RP3

Soo after almost 3 months of setting up I have my own LN full node running on RP3
I have been eager to try LN mainnet since the very beginning of it. I've found out about lnd, eclair, zap and other wallets but every scenario I tried to use it failed because of critical issues:
  • eclair does not really constitute a wallet, it's more like a credit card - you can send money but not receive it
  • lnd is okay, but requires a server and tons of resources for maintaining a full node, can't be used securely, efficiently and mobily at the same time
  • zap offers some cloud wallet (in testnet!) by default, this is a serious misunderstanding of my cryptoanarchy needs
  • web wallets - ah, forget it
So I've decided to use my Raspberry Pi with a very old laptop HDD attached (200GB so the pruning function has to be used) to create a backend wallet service and zap desktop (temporarily!) as my frontend control panel.
https://preview.redd.it/0vcq147887q11.png?width=1024&format=png&auto=webp&s=7bb6eccdd4110a857e5af0400acc2d7e1ee7ee85
Setting up Pi is easy, lots of tutorials over the internet, not gonna discuss it here. Then I had to obtain bitcoind (current rel: bitcoin-0.17.0-arm-linux-gnueabihf.tar.gz) and lnd (lnd-linux-armv7-v0.5-beta.tar.gz), create a bitcoin technical user, deploy the tools, configure and install new systemd services and go through the configs. This is a tricky part, so let's share:
# Generated by https://jlopp.github.io/bitcoin-core-config-generato # This config should be placed in following path: # ~/.bitcoin/bitcoin.conf # [core] # Set database cache size in megabytes; machines sync faster with a larger cache. Recommend setting as high as possible based upon machine's available RAM. dbcache=100 # Keep at most  unconnectable transactions in memory. maxorphantx=10 # Keep the transaction memory pool below  megabytes. maxmempool=50 # Reduce storage requirements by only storing most recent N MiB of block. This mode is incompatible with -txindex and -rescan. WARNING: Reverting this setting requires re-downloading the entire blockchain. (default: 0 = disable pruning blocks, 1 = allow manual pruning via RPC, greater than 550 = automatically prune blocks to stay under target size in MiB). prune=153600 # [network] # Maintain at most N connections to peers. maxconnections=40 # Use UPnP to map the listening port. upnp=1 # Tries to keep outbound traffic under the given target (in MiB per 24h), 0 = no limit. maxuploadtarget=5000 # [debug] # Log IP Addresses in debug output. logips=1 # [rpc] # Accept public REST requests. rest=1 # [wallet] # Do not load the wallet and disable wallet RPC calls. disablewallet=1 # [zeromq] # Enable publishing of raw block hex to 
. zmqpubrawblock=tcp://127.0.0.1:28332 # Enable publishing of raw transaction hex to
. zmqpubrawtx=tcp://127.0.0.1:28333 # [rpc] # Accept command line and JSON-RPC commands. server=1 # Username and hashed password for JSON-RPC connections. The field comes in the format: :$. RPC clients connect using rpcuser=/rpcpassword= arguments. You can generate this value with the ./share/rpcauth/rpcauth.py script in the Bitcoin Core repository. This option can be specified multiple times. rpcauth=xxx:yyy$zzz
Whooaa, this online config generator is really helpful, but I still had to manually correct a few things. The last line is obviously generated by rpcauth.py, I disabled the wallet functionality as lnd is going to take care of my funds. ZMQ is not available to the network so only my LND can use it, RPC usage I still have to think through a little, in general I would like to have my own block explorer some day but also be safe from any hacking attempts (thus I would need at least 2 RPC ports/user accounts - one for lnd, one for block explorer frontend). No ports open on firewall at this time, only UPnP is active and gently opens 8333 for block/tx transfers.
Now, synchronizing the blockchain took me time from mid-July to early September... The hard drive is really slow, also my external HDD drive has some trouble with its A/C adapter so Pi was getting undervoltage alerts all the time. Luckily, it is just downclocking when it happens and slowly but steadily synchronized the whole history. After all, I'm not paying even $5 monthly for a VPS, it is by design the cheapest hardware I could use to set up my LN wallet.
When bitcoind was ready (I've heard some stories about btcd but I don't trust this software yet, sorry), it's time to configure lnd.conf:
[Application Options] debuglevel=trace rpclisten=0.0.0.0:10009 externalip=X.X.X.X:9735 listen=0.0.0.0:9735 alias=X color=#XXXXXX [Bitcoin] bitcoin.active=1 bitcoin.mainnet=1 bitcoin.node=bitcoind [Bitcoind] bitcoind.rpchost=127.0.0.1 bitcoind.rpcuser=X bitcoind.rpcpass=X bitcoind.zmqpubrawblock=tcp://127.0.0.1:28332 bitcoind.zmqpubrawtx=tcp://127.0.0.1:28333 
Here I've had to XXX a little more fields, as not only the bitcoind RPC credentials are stored here, but also my node's public information (it should be illegal to run nodes without specifically selected color and alias!). It is public (and I had to open port 9735 on my firewall), but not necessarily connected to my reddit account for most of the adversaries, so let's keep it this way. In fact, I also see a security vulnerability here: my whole node's stability depends on the IP being static. I could swap it for a .tk domain but who can tell if the bad guys won't actively fight DNS system in order to prevent global economic revolution? As such, I would rather see node identification in LN based on a public key only with possible *hints* of last-known-ip-address but the whole discovery should be performed by the nodes themself in a p2p manner, obviously preventing malicious actors from poisoning the network in some way. For now, I consider the IP stability a weak link and will probably have to pay extra Bitcoin TX fees when something happens to it (not much of a cost luckily!).

https://preview.redd.it/hjd1nooo77q11.png?width=741&format=png&auto=webp&s=14214fc36e3edf139faade930f4069fc31a3e883
Okay then, lnd is up and running, had to create a wallet and give it a night for getting up to speed. I don't know really what took it so long, I'm not using Windows nor 'localhost' in the config so the issues like #1027 are not the case. But there are others like #1545 still open so I'm not going to ponder much on this. I haven't really got any idea how to automatically unlock the wallet after Pi restart (could happen any time!), especially since I only tried to unlock it locally with lncli (why would I enter the password anywhere outside that host?), but let's say that my wallet will only be as stable as my cheap hardware. That's okay for the beta phase.
Finally, zap-desktop required me to copy tls.cert and admin.macaroon files to my desktop. If my understanding of macaroon (it's like an authentication cookie, that can later be revoked) is correct then it's not an issue, however it would be nice to have a "$50 daily limit" macaroon file in the future too, just to avoid any big issues when my client machine gets stolen. Thanks to this, I can ignore the silly cloud-based modes and have fully-secure environment of my home network being the only link from me to my money.
https://preview.redd.it/11bw3dgw47q11.png?width=836&format=png&auto=webp&s=b7fa7c88d14f22441cbbfc0db036cddfd7ea8424
Aaand there it is. The IP took some time to advertise, I use 1ml.com to see if my node is there. The zap interface (ZapDesktop-linux-amd64-v0.2.2-beta.deb) lacks lots of useful information so I keep learning lncli syntax to get more data about my new peers or the routes offered. The transactions indeed run fast and are ridiculously cheap. I would really love to run Eclair with the same settings but it doesn't seem to support custom lnd (why?). In fact, since all I need is really a lncli wrapper, maybe it will be easy to write my own (seen some web gui which weighs 700MB after downloading all dependencies with npm - SICK!). Zap for iOS alpha test registration is DOWN so I couldn't try it (and I'm not sure if it allows custom lnd selection), Zap for Android doesn't even exist yet... I made a few demo transactions and now I will explore all those fancy t-shirt stores as long as the prices are still in "early investor" mode - I remember times when one could get 0.001 BTC from a faucet...
https://preview.redd.it/42sdyoce57q11.png?width=836&format=png&auto=webp&s=7ec8917eaf8f3329d51ce3e30e455254027de0ee
If you find any of the facts presented by me false, I am happy to find out more in the discussion. However what I did I did mostly for fun, without paying much attention to the source code, documentation and endless issue lists on github. By no means I claim this tutorial will work for you but I do think I shared the key points and effort estimations to help others decide if they want a full-node LN client too. I'm also interested in some ideas on what to do with it next (rather unlikely that I will share my lnd admin.macaroon with anyone!) especially if it gives me free money. For example, I can open 1000 channels and start earning money from fees, although I no longer have more Bitcoins than the LN capacity yields... I will probably keep updating the software on my Pi until it leaves beta phases and only then will pour more money inside. I'm also keen on improving the general security of my rig and those comments I will answer more seriously.
submitted by pabou to Bitcoin [link] [comments]

[FULOOSCOIN] Welcome to our Community and everything you need to know in a few minutes.

What is Fuloos Coin and why should we use it?

Fuloos Coin is an open-source digital currency, allowing merchants and users across the globe to send transactions fast and with low fees. We officially released Fuloos Coin on December 1st, 2017.
We are the next digital currency that uses the Scrypt Algorithm to allow users to transact their funds fast and with low fees across the world without delays with the ability to stake your coins to earn interest on your funds.
Fuloos Coin has grown a lot since we started in 2017, reaching other 20,000+ members supporting the community and the development team for the future of the Fuloos making us the most affordable cryptocurrencie for merchants and users around the world making it easier to pay for services, friends or employees with almost instant transactions.
Our main infrastructure is backed by multiple dedicated nodes to insure our network never goes down and allowing users to use Fuloos Coin any time of the day providing a secure and reliable environment for merchants with no downtime what's so ever.

Where can I buy Fuloos Coins?

Here's a list of the current exchange platforms that allow you to trade FLS with different cryptocurrencies:
We are hoping to be listed on many more exchanges over the coming weeks to improve the accessibility of purchasing coins and daily trading for Fuloos.
Any other questions regarding this? Please, contact one of the team members in one of the social chats we provide.

What is staking?

Staking also known as Proof-of-Stake or POS, is the ability for Fuloos Coin holders to earn interest on their funds with our inbuilt stake-miner into our desktop wallets which allows our network to run smoothly with our community support by validating transactions or by mining blocks just by keeping your wallet open.
For example, if I had 1000 Fuloos Coin's and if the transaction's dates have been longer than seven days, I could potentially earn 0.85 Fuloos Coin's every 10 minutes.
Technical Specifications:
If you would like to know more information about staking your funds, you can use our own calculator to find out how much you can earn.
Proof-of-Stake Calculator

Where can I store my coins?

There are several options on places to store your coins, starting from the exchange platforms which have inner wallets like Stocks.Exchange. However, the most secure way to store your coins is to keep it in outside wallets. Here’s a list of wallet options to store your coins:
Choose the best option that is suitable for you and don’t feel shy to ask us for help when setting up your wallet. Please, understand that your wallet is a source where you store your funds. Take it seriously, use all the available protection methods (backups, 2FA, complicated passwords).

Are there any local communities presented in my native language?

Definitely, Fuloos Coin is a cryptocurrencie with supporters all over the world. Be the first one to hear news in your native language and meet other users in our community!
You can see our community managers via our official team page on our website and also can ask questions in our chats to speak one of the community managers directly, if you have any suggestions for the Fuloos Team or your local community.

Can I use Fuloos Coin as a payment method? Is it possible to spend the coins in a store, shop, hotel, etc.?

Of course, you can purchase items or buy goods/services using Fuloos. We are currently working on our new merchant platform which will allow online store owners to accept Fuloos easily using a created plugin by our development team.
Popular E-commerce Platforms will be supported:
If you are a developer and would like to help create service or integrate Fuloos into your own website, you can use the created PHP Class created by LiteSpeed to make it easier to install and use, there will also be a c++ version released soon for programs integration.
https://github.com/LiteSpeedDev/FuloosRPC/

Social Links & Community Chats.

Following our social media and joining our community chats will allow you to keep up to date with the Fuloos Development and News relating to Fuloos Partners and Announcements.
The Fuloos team is glad to welcome every new user into our community. Join our family to be a part of one of the most prospective cryptocurrencies and enjoy it!
Yours truly,
LiteSpeed, CryptoKnight & the Fuloos Team.
submitted by Fuloos to Fuloos [link] [comments]

Help wanted: Network problem with Bitcoin Core Full Node and Samourai Wallet.

Hi all

I have port forwarding set up for TCP 8333 and TCP 8332.
Firewall says:
8332 ALLOW Anywhere
8332 (v6) ALLOW Anywhere (v6)
...
8333 ALLOW Anywhere # bitcoin mainnet
8333 (v6) ALLOW Anywhere (v6) # bitcoin mainnet

I'm able to reach 8333 using https://www.yougetsignal.com/tools/open-ports/ - but 8332 is closed .

here is the RPC config from ~/.bitcoin/bitcoin.conf
# Connection settings
rpcuser=XXX # user replaced
rpcpassword=XXX # password replaced
rpcallowip=192.168.X.X # IP replaced
zmqpubrawblock=tcp://127.0.0.1:28332
zmqpubrawtx=tcp://127.0.0.1:28333
rpcbind=0.0.0.0
rpcport=3882
rpcallowip=127.0.0.1
rpcallowip=X.X.X.X # public IP replaced

netstat -na |grep 8332
tcp 0 0 127.0.0.1:283320.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:83320.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:28332127.0.0.1:44296ESTABLISHED
tcp 0 0 127.0.0.1:44296127.0.0.1:28332ESTABLISHED
tcp6 0 0 ::1:8332 :::* LISTEN


I try to use my node in combination with the awesome Samourai Wallet. https://samourai.kayako.com/article/40-configure-your-node-for-samourai-wallet

submitted by xavierfiechter to Bitcoin [link] [comments]

1mb Fork Txn

Enclosed find a signed 1mb txn (999,957 bytes), that if mined will fork the network. TxnID: bbb67fc3320d1e9a58c7cd0bb5ead2cff87b243e089e4a21dad669ba28703f32
The outputs of this transaction have the following function, designated by their prefix:
The 1mb signed txn: https://anonfile.com/N2T4Aeb0bb/1mbtxn.txt
Once a client is available that will support relay of this txn, the console interface will likely not support it. To push this txn you'll have to use the RPC interface with a script https://en.bitcoin.it/wiki/API_reference_(JSON-RPC)
from bitcoinrpc.authproxy import AuthServiceProxy, JSONRPCException
rpc_user="Your_User"
rpc_password="Your_Pass"
rpc_connection = AuthServiceProxy("http://%s:%[email protected]:8332"%(rpc_user, rpc_password))
txn = []
f = open('1mbtxn.txt', 'r') #This is the above linked txt file containing the txn
txn = f.read()
f.close()
print(rpc_connection.sendrawtransaction(txn))
if you get this error, your client does not support this txn
64: tx-size
submitted by 1MBforKTR1gAqRLkNbQg to btc [link] [comments]

Ravencoin Open Developer Meeting - 2/15/2019

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:02 PM
Hello everybody!

theking - Last Friday at 2:02 PM

Seems likes it’s been so long since this meeting was held. At least a month 📷

Tron - Last Friday at 2:02 PM

Hi all!!!

Tom - Last Friday at 2:02 PM

Big boss is here !(edited)

BigZim - Last Friday at 2:03 PM

Oh hi

theking - Last Friday at 2:04 PM

Hi @Tron

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:04 PM

Topics for today: Release 2.2.2, Mobile Wallet, Restricted Assets, SLC Raven Meetup📷1

truedev - Last Friday at 2:05 PM

hello

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:05 PM

Release 2.2.2 GO

J. | ravenland.org - Last Friday at 2:05 PM

Hey

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:05 PM

BTW, blondfrogs won't be able to join us today. 📷

corby - Last Friday at 2:05 PM

Hi all

Chatturga - Last Friday at 2:05 PM

Blondefrogs has been working on the 2.2.2 update. He isnt here today, but he left this tidbit for the meeting:(edited)"Release 2.2.2 has a bunch of new updates. The sync speed fix that was released in 2.2.1 has been updated even more to use less memory/ram and uses less CPU. Each node used to hold all addresses that contained an asset as well as the amount in those addresses. That is now optional with the -assetindex flag. Which can be put into the raven.conf or added as a parameter when starting the wallet. Some other wallet issues were also fixed with this memory update. This is considered an mandatory update, especially if you haven't updated to 2.2.1 which resolved a potential fork bug fix. I would still suggest updating to 2.2.2 even if you are on 2.2.1."📷6

Jeroz - Last Friday at 2:07 PM

wen source?📷1

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:07 PM

There's a PR that was just moved to Develop.When is now

Jeroz - Last Friday at 2:08 PM

great 📷

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:08 PM

It'll be merged by the devs to master and then binaries should be posted soon

truedev - Last Friday at 2:09 PM

any idea when dividends will be functional?

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:09 PM

A bunch of testing has been happening and is currently running on the seed-nodes.

Tron - Last Friday at 2:10 PM

No timeline for dividends, but it is the one function that doesn't need any changes to consensus. And it can be done on tier 2 with a python script. The plan is still to build in a rpc call.📷2

truedev - Last Friday at 2:11 PM

alright

SpyderDev - Last Friday at 2:12 PM

We have been focusing on sync performance and have been running many tests. I've added an image of the results of this testing. Currently we still want to work on getting the Windows QT sync times faster (at least closer to what they are using just ravend). Overall we are very happy with the speeds and hope it will help people that have struggled getting their nodes up to date.(edited)📷

Jeroz - Last Friday at 2:13 PM

Yeah that table completely puzzled me

[Master] Roshii - Last Friday at 2:13 PM

hello!📷6

Jeroz - Last Friday at 2:13 PM

Fast branch is 2.2.1? or 2.2.2? Develop branch is 2.2.0?

SpyderDev - Last Friday at 2:15 PM

Sorry, should have clarified that. I was testing while it was still under development. On the table the top is the new-sync code, the bottom is the old "assets" release. As of about 5 minutes ago all of this code is on the develop branch.

Jeroz - Last Friday at 2:15 PM

Although syncing is mostly bottlenecked by cpu speed, that 16 core windows-qt still looks off to me. I synced windows Qt using 2.2.2 in ~2h on a i5-7600K.ok

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:17 PM

Okay, we good to move to the Mobile update?

SpyderDev - Last Friday at 2:17 PM

The Windows box is an AWS instance and there is some concern that the remote desktop could be slowing the QT UI down causing the horrible sync times. I am working on getting a local Windows 10 resource and will have updated information once that is ready (early next week).

Jeroz - Last Friday at 2:18 PM

ah that might explain. Ubuntu qt was 45 mins for me

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:18 PM

CoolOkay, Mobile!Go!

[Master] Roshii - Last Friday at 2:18 PM

📷📷1

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:19 PM

@[Master] Roshii has been working closely with some of the other devs to get the iOS version out the door.Android will follow closely.

Jeroz - Last Friday at 2:20 PM

is android an easy port?

J. | ravenland.org - Last Friday at 2:20 PM

Usually its the case(?), i mean easier 📷(edited)

SpyderDev - Last Friday at 2:20 PM

Just copy and paste right Roshii 📷

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:20 PM

LOLNo, usually its a completely new development effort.For the RVN Wallets they are both written in native iOS/Android code.

[Master] Roshii - Last Friday at 2:21 PM

So the iOS and Android use the same Core SPV module written in C, and it's the most difficult part.I have already did some work when it comes to Android, and it's 70% finishedHave also to port all the changes we lately did to the iOS wallet ...

boatsandhoes - Last Friday at 2:21 PM

yeah, unfortunately its not as easy as cut and paste for ios to android

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:21 PM

Anybody interested in installing the TestFlight version and helping us test?

boatsandhoes - Last Friday at 2:22 PM

yes

J. | ravenland.org - Last Friday at 2:22 PM

For android? sure.

BW__ - Last Friday at 2:22 PM

Android? yes.(edited)

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:22 PM

I'll talk to Apple about adding Android support to TestFlight.Might be a while.

J. | ravenland.org - Last Friday at 2:22 PM

lol

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:22 PM

Anybody on here using iOS?

Jeroz - Last Friday at 2:22 PM

Yeh me

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:22 PM

besides me...

[Master] Roshii - Last Friday at 2:23 PM

Android is very close, fortunately I'll have enough coffee in Morocco to finish the wallet in two weeks.(edited)📷4📷5

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:23 PM

https://testflight.apple.com/join/NTVQ2FfY (400 installs available)Join the RVN Wallet betaAvailable on iOS📷

theking - Last Friday at 2:23 PM

I will test iOS if needed

[Master] Roshii - Last Friday at 2:23 PM

@shiny

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:24 PM

Some of the devs have been doing a bunch of testing on iOS but we would love others to help.Bugs can be reported on GitHubhttps://github.com/RavenProject/ravenwallet-iosGitHubRavenProject/ravenwallet-iosContribute to RavenProject/ravenwallet-ios development by creating an account on GitHub.📷

truedev - Last Friday at 2:25 PM

how confident are you that apple will allow it on the appstore

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:25 PM

It's already in the App store.

truedev - Last Friday at 2:25 PM

ok

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:25 PM

That wasn't easy though.

truedev - Last Friday at 2:26 PM

yah figured, a lot of coins have been completely rejected(edited)

Chatturga - Last Friday at 2:26 PM

The devs already jumped through Apples 152,315 flaming hoops to get it in there.

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:26 PM

Yup, many meetings and phone calls.

J. | ravenland.org - Last Friday at 2:26 PM

wen rvn modular phone

Jeroz - Last Friday at 2:27 PM

Looking good📷📷7

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:28 PM

Okay, any questions about iOS release?

jaysonb - Last Friday at 2:28 PM

seed word format changed? i seem to have to have same words. did i need to delete and install fresh?

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:29 PM

No, it used your old ones.Always have your 12 words. especially when testing.

ravencoin maximalist 🧘🏻♂ - Last Friday at 2:30 PM

I’ve got iOS

Tron - Last Friday at 2:30 PM

If you use your 12-words, and then sync, and you're missing funds. Go here: https://medium.com/@tronblack/ravencoin-testing-ios-wallet-b713deb2c800MediumRavencoin — Testing iOS Wallet – Tron Black – MediumThank you for helping us test the Ravencoin iOS mobile wallet. Since you are in an early group of testers, you might have used the…

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:30 PM

Sweet, install and report bugs.

Tron - Last Friday at 2:30 PM

Or just go there...

jaysonb - Last Friday at 2:30 PM

that article scared me so i moved everything off.but i'll put some back on now

ravencoin maximalist 🧘🏻♂ - Last Friday at 2:31 PM

📷

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:31 PM

That's unfortunate. You don't need to be scared ever if you have your 12 words.

[Master] Roshii - Last Friday at 2:31 PM

android current state(edited)📷

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:32 PM

Here's the install link one more time for those that have joined late: https://testflight.apple.com/join/NTVQ2FfYJoin the RVN Wallet betaAvailable on iOS📷Okay, Tron's topic: Restricted Tokens

Tron - Last Friday at 2:33 PM

I have an idea.(edited)📷7📷6

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:34 PM

That several other devs have helped with. 📷

Tron - Last Friday at 2:34 PM

📷

SpyderDev - Last Friday at 2:34 PM

and lawyers

Tron - Last Friday at 2:34 PM

When the project started, ICOs were the big thing. Now it is STOsThe main difference is the legal wrapping and rules around securities.If Ravencoin has two more token types (Tags and Restricted Assets), there are lots of ways to make compliant tokens.Importantly, it doesn't affect the existing tokens at all.Tags - Tokens that can be sent only by the issuer once (with metadata).These tokens start with (hashtag)(edited)📷8

SpyderDev - Last Friday at 2:37 PM

^(octothorpe)

Tron - Last Friday at 2:37 PM

The Restricted Assets start with $, and can be frozen by the issuer. But they only move between tagged addresses.(edited)

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:38 PM

Tags can be sent to a user's address after the issuer has done the necessary due diligence for an STO issuance.(edited)

Tron - Last Friday at 2:38 PM

The issuer determines which tags the Restricted Asset will honor.This can be used for lots of different use cases.

EEE - Last Friday at 2:38 PM

Stunning interface guys

boatsandhoes - Last Friday at 2:39 PM

will that determination be a setting in the wallet?

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:39 PM

Restricted assets can then only be sent to addresses that are allowed and have the proper Tags.

boatsandhoes - Last Friday at 2:39 PM

interesting📷1

J. | ravenland.org - Last Friday at 2:39 PM

Did you guys get contacted by some entity* whos forcing the restricted address policy? or is this done as precautionary measure? At first glance your idea sounds good Tron.(edited)

Tron - Last Friday at 2:39 PM

Example: $UBER token only moves among addresses tagged with #KYC

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:40 PM

So Ravenland will have to buy a bunch more spam tokens.📷4

SpyderDev - Last Friday at 2:40 PM

#ravenland.

boatsandhoes - Last Friday at 2:40 PM

so is the $ something that can be added to an existing asset?

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:40 PM

It's not a forced thing. But adding the ability for Raven to be used in new use cases where legal requirements exist.

Tron - Last Friday at 2:40 PM

Not contacted by anyone, and not precautionary. Ravencoin Assets are just tools. This is just another tool that will help issuers of security tokens.📷9📷4

BW__ - Last Friday at 2:41 PM

Love it.

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:41 PM

It'll be a new token type that you can create @boatsandhoes📷1

ravencoin maximalist 🧘🏻♂ - Last Friday at 2:41 PM

That sounds awesome

SpyderDev - Last Friday at 2:41 PM

I for one am very excited about this...📷4

Hans_Schmidt - Last Friday at 2:41 PM

How does the $ token owner specify the required # tags?

DeejayQQ - Last Friday at 2:41 PM

Can the same name have different token type?Sorry need time to digest

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:42 PM

Still working out the details. Tron will be posting additional info about the idea soon.

Steelers - Last Friday at 2:42 PM

Cool

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:42 PM

Feedback is wanted!

Tron - Last Friday at 2:42 PM

Q: Was this originally the plan for Ravencoin? A: No. This is in response to the regulatory ramp up in 2018 in some jurisdictions which requires that only known individuals or entities to operate peer-to-peer on certain tokens. For jurisdictions that allow unrestricted peer-to-peer transfer, we strongly encourage use of the original Ravencoin assets. The Restricted Assets are an adaptation to satisfy burdensome, privacy-destroying regulations, with a goal of reducing information replication which makes Ravencoin Restricted Assets a better alternative to those being promoted now.

jaysonb - Last Friday at 2:43 PM

all nodes will validate the transactions not just those interested in the transaction - i assume all will validate..

boatsandhoes - Last Friday at 2:43 PM

so essentially any name already secured in the hopes of having that functionality are worth less because they wont be able to?

theking - Last Friday at 2:44 PM

Can the restricted assets be time based in any way? For instance, in some STO regulated environment, there is a lockup for some period of time after issuance, but then after a certain period of time the restriction goes away and the securities can be traded. Is that contemplated at all?

DeejayQQ - Last Friday at 2:44 PM

If I already have Tron as my asset, there could be another Tron but under a different token type such as restricted assets?

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:44 PM

Yes all nodes will do consensus checks.

corby - Last Friday at 2:44 PM

@boatsandhoes there's going to be a grace period where you can purchase $XXX if you own XXXon the order of months

boatsandhoes - Last Friday at 2:45 PM

📷 📷 📷 📷

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:45 PM

Yes, you have the TRON asset and you can also have the $TRON asset.(edited)

Tron - Last Friday at 2:45 PM

Regarding the lockup....

boatsandhoes - Last Friday at 2:45 PM

how many RVN for that?

Tron - Last Friday at 2:45 PM

Rule 144 under the Securities Act of 1933 This is an important rule to be aware of in terms of privately held securities. This rule provides the most commonly used exemption for holders to sell restricted securities (Note: For context, a restricted security is a security sold in an exempt offering, except for Reg A+). The general idea is that you can publicly resell your “restricted” (privately sold) securities only when the restricted legend is removed. The solution Ravencoin Restricted Assets provides is the ability for the Iissuer to Freeze the asset ininto the holders account. The qty will be visible, and the frozen status will be visible. The meta-data for a Freeze can specify 144_Restricted. The issuer can Unfreeze to release the 144 restriction.Similar for Reg D 1-year lockup.@theking

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:46 PM

@theking ^^

DeejayQQ - Last Friday at 2:46 PM

What is the timeline for this restricted asset to be implemented?📷1

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:46 PM

No timelines yetStill in the ideation phase.

SpyderDev - Last Friday at 2:46 PM

Fresh off the press...

DeejayQQ - Last Friday at 2:46 PM

Ok, idea for nowGot it

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:46 PM

Wanting input for the idea.

boatsandhoes - Last Friday at 2:47 PM

a preset for lock up settings would be nice

Jeroz - Last Friday at 2:47 PM

What about the ability to move an asset from restricted to unrestricted after grace period similar to the reissue ability? By the issuer(edited)

boatsandhoes - Last Friday at 2:47 PM

adjustable preset*

DeejayQQ - Last Friday at 2:48 PM

If this restricted assets would help underlying token listed on exchanges for trading by satisfying the legal requirements, I don’t see why not. There are only benefits📷2

boatsandhoes - Last Friday at 2:48 PM

yeah, win win

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:48 PM

There is something similar in vote tokens.

corby - Last Friday at 2:48 PM

@Jeroz the issuer would be able to "reissue" and relax restrictions

DeejayQQ - Last Friday at 2:48 PM

Just throwing things out here. Can we just make all existing tokens crested so far restricted assets?*created

boatsandhoes - Last Friday at 2:49 PM

stupid question, is it possible to have burned rvn cost for the $ to add onto the block reward as a bonus?(edited)

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:49 PM

No, @DeejayQQ there should be both usecases available in the platform.

corby - Last Friday at 2:49 PM

We (my dog and I) are envisioning a differentiated space where we can charge a lot more RVN to keep non-serious people out..(edited)

Tron - Last Friday at 2:49 PM

@Jeroz Yes, as long as the asset is still "reissuable", you could change the logic from (#KYC & #ACCREDITED) to just #KYC📷3

Jeroz - Last Friday at 2:49 PM

I'm just worrying about the name uniqueness if you can have #BANANA and $BANANA

BW__ - Last Friday at 2:50 PM

Is it fair to assume that tags can be standardized for specific purposes? If so, should we create something akin to an 'ERC' in git repo?

Jeroz - Last Friday at 2:50 PM

@Tron sounds cool

truedev - Last Friday at 2:50 PM

honestly, I think you should be able to buy/create an asset in a set, with all types(edited)

boatsandhoes - Last Friday at 2:50 PM

^that part

Hans_Schmidt - Last Friday at 2:51 PM

Since the #KYC tag is just locked to an address, what prevents someone from selling their address and thereby the KYC?

corby - Last Friday at 2:51 PM

The "#" types won't trade -- they're just stamps to stamp addresses as qualified-to-hold-some-stuff..

Tron - Last Friday at 2:51 PM

The tags are created by the users. The system is still jurisidiction agnostic.

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:51 PM

@Hans_Schmidt nothing really, the same thing as selling your username password to any other existing financial app account.

corby - Last Friday at 2:51 PM

@Hans_Schmidt Real world networks, high cost of entry (for serious applications)For non-serious applications, nothing

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:51 PM

You still have the liability associated with that account though.

Jeroz - Last Friday at 2:52 PM

@corby what about BANANA/ vs $BANANA/ ?Or do you want to make them subassets?

boatsandhoes - Last Friday at 2:52 PM

@Jeroz better safe than sorry, just swoop both

Tron - Last Friday at 2:52 PM

A country could require that #SOMECOUNTRY tag has to exist before moving $SPECIALASSET to an address. The users set the rules. #KYC was just an example because it is an industry problem at the moment.

corby - Last Friday at 2:52 PM

#BANANA, $BANANA, TRICYCLE, and BANANA can all coexist just fine I think..

theking - Last Friday at 2:53 PM

Thanks @Tron. This is great and I think something that will enable raven to become an even more widely used platform.📷4

Tron - Last Friday at 2:53 PM

That's the hope. I think it solves some real problems that the industry is trying to solve through incompatible ERC-20 experiments.📷3

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:54 PM

/hacks📷3

boatsandhoes - Last Friday at 2:54 PM

what is the purposed cost for $ in addition to an existing asset?

corby - Last Friday at 2:54 PM

People that own #THESE I am calling "Qualifiers" -- they just stamp their mark on addresses. Issuers of $THESE need to establish trust with #THESE and #THOSE and then decide what restrictions to apply.📷1

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:54 PM

5 mins left. Stay on this topic or switch to meetup?

Tron - Last Friday at 2:55 PM

@boatsandhoes Not determined.

Jeroz - Last Friday at 2:55 PM

yeah the idea is a nice proof of ownership / membership

DeejayQQ - Last Friday at 2:55 PM

Meetup

Chatturga - Last Friday at 2:55 PM

TL;DR - The SLC meetup is in 1 month. Go to https://www.meetup.com/Salt-Lake-City-salt-lake-city-Meetup/ to indicate if you plan on attending so that we have a somewhat accurate headcount.MeetupSalt Lake City Ravencoin (Salt Lake City, UT)Ravencoin is a blockchain and platform optimized for transferring assets, such as tokens, from one holder to another, and is built on a fork of the Bitcoin code. It is intended to prioritize security,📷

corby - Last Friday at 2:55 PM

@boatsandhoes One Million Raven

Chatturga - Last Friday at 2:55 PM

Punch and pie

J. | ravenland.org - Last Friday at 2:56 PM

Can the SLC meetup made interactive for people that cant make it there?

theking - Last Friday at 2:56 PM

What about having just one name ( you first buy the standard raven token under whatever name you like) and then the holder of the owner token is the only one to create restricted tokens ? Might be some way to ensure no name confusion.📷4

boatsandhoes - Last Friday at 2:56 PM

what about that block reward bonus concept for purchasing $. would that work?

Chatturga - Last Friday at 2:56 PM

I dont know that we have the ability to make it interactive as far as Q&A goes, but I'll look into it. We should have it live streaming. @J. | ravenland.org(edited)📷2

BW__ - Last Friday at 2:56 PM

@Tron Is there same kind of logic layer to restricted assets?(edited)

Tron - Last Friday at 2:57 PM

@theking I like that idea.

Jeroz - Last Friday at 2:57 PM

Quick question that is offtopic but I think deserves an answer because it was asked a couple of times earlier this week: Will unique assets get a reissuable function? To change IPFS.(edited)📷2

Tron - Last Friday at 2:57 PM

@BW__ Yes. Simple and, or, not and parenthesis - limited in length.(edited)

boatsandhoes - Last Friday at 2:57 PM

@theking thats a good idea

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:58 PM

@Jeroz There is not a way to do that currently.

BW__ - Last Friday at 2:58 PM

@Tron That makes sense. Thank you.

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 2:58 PM

Just make sure your changes to the information have the same hash as the previous data and your golden. 📷📷1

Jeroz - Last Friday at 2:59 PM

Any plans on changing that, perhaps when introducing new types of assets?

boatsandhoes - Last Friday at 2:59 PM

i like that it cant be changed

corby - Last Friday at 3:00 PM

Thanks everyone!

theking - Last Friday at 3:00 PM

@Tron there was some info floating around about a 2nd later KYC solution ( from your recent podcast w Crypto Koala). Is that a separate solution someone is working on or part of this new concept?📷1

Tron - Last Friday at 3:01 PM

Starting with the introduction of messaging, every transaction can have an IPFS hash. Can be used as an public invoice, details about the transaction, etc.@theking The same new concept.

[Master] Roshii - Last Friday at 3:02 PM

Ok, we're done.

Steelers - Last Friday at 3:02 PM

How would Raven handle for instance a stock split?

BW__ - Last Friday at 3:02 PM

Are there sync concerns if a restricted asset logic layer is added?

Tron - Last Friday at 3:02 PM

@theking The KYC provider would store the KYC info, and send the Tag to an address with meta data that specifies that they're holding the KYC data. The KYC data would not be public, but could be audited.

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 3:02 PM

That way you could update information about the original unique asset with each transaction.@Steelers Just a simple re-issue of the asset

Tron - Last Friday at 3:03 PM

@bw_ The logic layer is only a small db that stores the meta-data about the Restricted Asset, and enforces the restriction in the consensus rules. Rule returns true/false.(edited)

RavencoinDev (Jesse/Wolfsokta) - Last Friday at 3:03 PM

Thanks everybody! I have to run.

Jeroz - Last Friday at 3:04 PM

I'm looking forward to the discussions to let this take shape. Thanks all! 📷📷4

Tron - Last Friday at 3:05 PM

@BW__ It would work very similarly to the way the units works now. Each asset has number of units and any transaction that makes it too granular (more satoshis) will fail in consensus -- even if it gets past the RPC checks.Signing off. Thanks all!!!📷9📷4📷9
submitted by Chatturga to Ravencoin [link] [comments]

Bitcoin JSON-RPC Tutorial 6 - JSON Parameters and Errors Forgot My Bitcoin Wallet Password! How to recover your BTC.com wallet if you forgot the password  Wallet Tutorial  BTC.com Bitcoin JSON-RPC Tutorial 3 - bitcoin.conf Bitcoin RPC Remote Code Execution Exploit for BitcoinCore 0.9-0.15.1 CVE-2017-9230

No you can define the rpcuser and rpcpassword in the bitcoin.conf file itself. Usually it is commented , you can uncomment the line rpcuser and rpcpassword and input your username and password which will be used when you will be connecting to your bitcoind through HTTP JSON RPC. How to Do RPC Calls with C++ Bitcoind . bitcoin deamon = core value of the software (bitcoind -printtoconsole -debug=1) Bitcoind provide the RPC "interface" in which user can query with bitcoin-cli (or a library in c++). You must run bitcoind before using bitcoin-cli. Obviously this is a security vulnerability - an eavesdropper can easily determine the user name and password. In the case of basic HTTP authentication like this, the connection is not secure unless the exchange takes place over HTTPS(TLS). The Bitcoin RPC API does not allow connection via SSL - this functionality was dropped in 2015. A come fare soldi con network marketing web based interface to the bitcoin default rpc password Bitcoin API { "result": Bitcoin Core Released How to Keep Your Bitcoin Safe and Secure WIRED Troubleshooting Tips for Armory Bitcoin Armory Proj Bitcoin 1: Withdraw the funds to the address stated on the website of the Bitcoin Testnet Faucet Bitcoin-development] [PATCH] bitcoind:. Bitcoin Core da pra ganhar dinheiro vendendo cupcake will automatically detect how many cores your system bitcoin core rpc username password has, and create that number of threads for transaction and block validation.Added a new user on Ubuntu, set password not working?

[index] [18054] [11454] [2214] [10683] [9670] [27382] [69] [27757] [11104] [24945]

Bitcoin JSON-RPC Tutorial 6 - JSON Parameters and Errors

Bitcoin JSON-RPC tutorial. Handling JSON, entering parameters and receiving error messages. BTC: 1NPrfWgJfkANmd1jt88A141PjhiarT8d9U. Bitcoin JSON-RPC Tutorial 4 - Command Line Interface - Duration: 5:14. m1xolyd1an 10,986 views. 5:14. Investigation of the effect of Cracks on Vibration Parameters of A Cantilever Beam WEBINAR ... Bitcoin JSON-RPC tutorial. How to set up and use bitcoind wallet notify feature. My Book: Building Bitcoin Websites - https://www.amazon.com/Building-Bitcoin... Bitcoin JSON-RPC tutorial. How to set up bitcoind on a VPS. BTC: 1NPrfWgJfkANmd1jt88A141PjhiarT8d9U. Recover your Bitcoin Core wallet password with btcrecover - Duration: 12:25. Bitcoin Daytrader 18,514 views. 12:25. The first 20 hours -- how to learn anything Josh Kaufman ...

Flag Counter