Bitcoin Core :: Bitcoin

Created a full node + Lightning node from scratch.

So i created a full node and a lightning node from scratch.
Coming back to bitcoin after few years, i wanted to see what the lightning network was.
So i changed my vps to a dedicated server (to add more storage) and started my journey.
The first thing was to install the full node. there's some nice ressources to do that, but you have to find them. I started with https://bitcoin.org/en/full-node#other-linux-daemon but the cli instructions are almost non existent. I then found https://github.com/BlockchainCommons/Learning-Bitcoin-from-the-Command-Line which is great! Protip: you have to create a config file by yourself. I created a wallet and waited for the blockchain to finish downloading.
Then i added a lightning node. I used lnd because i like the go language. The program is great but i found the user documentation lacking. https://gist.github.com/bretton/0b22a0503a9eba09df86a23f3d625c13 is a nice ressource, but you don't need to set an rpc user, lnd will use the cookie auth automagically if you're running as the same user as bitcoind (and provide bitcoind path probably..?). Protip: To create a qrcode with your lightning address you can use qrencode: lncli newaddress p2wkh qrencode -o address.png 'bitcoin:bc1youraddress...'
Once everything looked to run smoothly i wanted to add funds to my lightning wallet. Protip: you can directly transfer fund to it. no need to transfer funds in your full node wallet (don't know why i did that..).
I manually opened few channels with other nodes, but using the autopilot feature from lnd seems to work fine.
Lastly, i wanted some sort of dashboard so i added https://github.com/djmelik/lndash because i'm fluent in python , the project is straightforward, read only, and good looking.
You can check my node at https://ln.xec.sh/
If you have any questions or remark, don't hesitate. Hope it can help someone else.
submitted by wiredmachine to Bitcoin [link] [comments]

Adding Monero support to a P2P game, need some advice

Hello everyone,
I'm currently in the process of adding Monero support to a peer-to-peer game I've been working on and would like to ask this community for some advice.
The application has a few hard requirements that must be met:
  1. The Monero integration must be done using JavaScript (primarily for Node but browser's okay too).
  2. The application must be able to create addresses and accompanying private keys internally (no CLI or external API). Preferably, these should be derived addresses using a master or main one (like HD wallets in Bitcoin).
  3. The application must be able to generate raw transactions internally -- no CLI or or external API. For this part let's assume that the input UTXOs are going to be available somehow (from a database, for example).
  4. The application must be able to sign raw transactions internally -- no CLI or or external API.
When I say "no CLI", I mean no RPC wallet or daemon; no external API calls either.
Essentially, I should be able to do the above offline, using JavaScript only, and then just post the signed transactions later (this part can be done via CLI or API). These are core requirements for the project otherwise I'd just use RPC or a service and save myself a lot of work.
So my question is: is there a documented JavaScript library that supports all of the above functionality?
I found a project called mymonero-core-js which appears to do what I'd need, but there doesn't seem to be any accompanying documentation (the included unit tests don't offer much information). Does this documentation exist?
There's also an offline wallet generator but it's also undocumented and kinda unwieldy (one huge file).
The game (my project), already supports Bitcoin and Bitcoin Cash using these constraints, and I've done fairly extensive work with Ethereum, smart contracts, and crypto in general (not just cryptocurrencies, I mean), so I shouldn't need much hand-holding.
Thanks muchly in advance!
P.S. It's not my intention to advertise my project so I haven't posted a link but I'll be happy to share if anyone asks.
submitted by monican_agent to Monero [link] [comments]

BCH JSON RPC Calls List?

Hi all, trying to find documentation for the list of JSON RPC calls for Bitcoin Cash. This is as close as I can get, and it says it's outdated.
submitted by jeffthedunker to Bitcoincash [link] [comments]

2020.5.18 - 2020.5.29 Bi-Weekly Report Updated

2020.5.18 - 2020.5.29 Bi-Weekly Report Updated
https://preview.redd.it/hnsjgxkz1o151.png?width=1250&format=png&auto=webp&s=ac891e2fe3ba853cbd4f3714fdefb641c8236463

Keywords in this issue:
Technology: privacy function, mainnet 4.0, blockchain explorer
Business: No update in these two weeks
Operations: 520 Day activity, Mainnet 4.0 technical document, Bitcoin Pizza Day, BSN

R&D Progress

Current progress
Continuous technical perfection of INT main chain
  • Regarding test of WASM standard, finding and fixing bugs is ongoing(72%)
  • Optimize the RPC interface of two consensus data queries (100%)
  • Development work of privacy function (mainnet 4.0) is ongoing (70%)
  • Optimize the mainnet block data synchronization, greatly improving the stability and efficiency of data synchronization (100%)
Perfection of INT wallet and Explorer
  • Continue to improve the mainnet Web wallet and revise the part of interface
  • Continue to improve the blockchain explorer and revise the part of interface
  • Continue to optimize the Mobile wallet and optimize the function of Red Packet
  • Continue to optimize testnet explorer of the mainnet 4.0
  • Continue to optimize web wallet of the mainnet 4.0 testnet.

Activity operation

Current progress
  • INT Chain Mainnet 4.0 Technical Documents Released
INT Chain mainnet 4.0 technical documents released on May 15. The technical documentation makes it easy for users to access the new mainnet and participate in testing. You can check here: https://titansdocs.intchain.io/
https://preview.redd.it/uiqoznb12o151.png?width=554&format=png&auto=webp&s=76be5f8a5e08426de41bde36eb26a1f9b5a7ccae

  • An article Details INT Chain Became a Qualified BSN Developer
INT Chain became a qualified BSN developer On May 9. To let more people know it, INT Chain gives the details about what BSN is, what services BSN provides, and what is the meaning of INT Chain as a qualified BSN developer. More details are shown here https://link.medium.com/3GKRv2O7I6
https://preview.redd.it/mb09yic32o151.png?width=296&format=png&auto=webp&s=4d970404936b927fc3f902670ce2b88600ae5d0f

  • 520 Day Activity Launched
Since the pronunciation of number 520 sounds similar to “I love you” in Chinese, May 20 has become another occasion for local people to convey their love to their significant others. So INT Chain released an activity, which encourages community members to convey love to their loved ones in Weibo.4 lucky people will get an INT custom T-shirt and token reward.
https://preview.redd.it/e2e1u4v42o151.png?width=235&format=png&auto=webp&s=194d87389076f096a31fbf2241133270dc3601e9

  • Bitcoin Pizza Day 10th Anniversary Activity Launched
On May 22, 2010, when bitcoin was a little over a year old, a developer named Laszlo Hanyecz bought two pizzas for 10,000 BTC. He is known as the first person to use bitcoin in a commercial transaction. The day is now known as "Bitcoin Pizza Day." To memory this event, INT Chain launched the "Bitcoin Pizza Day 10th Anniversary Activity", all users who share the poster in their WeChat moments have the chance to win a pizza.
https://preview.redd.it/hjqwq6962o151.png?width=209&format=png&auto=webp&s=d5717117639623ff31450011564e31aa31ff352a
submitted by INTCHAIN to INT_Chain [link] [comments]

ETHEREUM FRONTEND JAVASCRIPT APIS: WHAT YOU NEED TO KNOW

ETHEREUM FRONTEND JAVASCRIPT APIS: WHAT YOU NEED TO KNOW

https://preview.redd.it/9djdo90nx9051.jpg?width=2400&format=pjpg&auto=webp&s=54ca700da20bac0692ed294a31e75cfefb96f671
Blockchain has emerged as a popular technology, and if you are planning to make a career in this field, then there are various certification programs. When we talk about Blockchain, then it becomes important to mention about Ethereum. It is a cryptocurrency and an open-source platform as well. There has been some great development in this field, and those who are planning to learn about Ethereum must go for a certified Ethereum course.
Blockchain developers who are developing apps on Ethereum must know about the different frontend javascript which can simplify their task. In this blog, we will be highlight three such popular javascript APIs.
Ethereum Overview:
Ethereum emerged after Bitcoin and has now become a popular Blockchain platform. It is a cryptocurrency as well. It is an open-source software platform. Ethereum offers a flexible platform to the developer so that they can develop decentralized apps with ease.
Although scalability is a bit of an issue with Ethereum, in the current scenario, it is one of the best platforms for decentralized application development.
Looking at the broader spectrum and use of Blockchain, it has become a great career opportunity for many. Hence, option for certified Blockchain Developer is the right way to give your career the right boost.
What is API?
API is a set of the protocol which is used of building and integrating the applications across different platforms. APIs eventually simplifies app development and enables seamless interaction of your products and services with the user.
Popular frontend Javascript APIs:
Web3.js- This is a collection of libraries which empowers you to connect with remote Ethereum node. It is achieved by using HTTP or IPC connection. This is used for the following :

  1. Send ether from one account to another
  2. Interact with smart contracts
  3. Retrieve user account
It interacts with Ethereum Blockchain with JSON RPC protocol. A copy of all the data and code is present on the Blockchain. The API requests an individual Ethereum node with JSON RPC to read and write data to the network.
Ethers.js
Another frontend javascript is Ethere.js, which is used by most of the decentralized application developers owing to its features and functionalities. It has the following main features:

  1. It is open source
  2. It is completely safe as it keeps private keys restricted to the clients
  3. You can import and export using JSON wallets which again adds to the security feature
  4. Import and export BIP 39 mnemonic phrases
  5. You can connect to Ethereum nodes via JSON-RPC, MetaMask, INFURA, or Etherscan.
  6. It is completely TypeScript ready
  7. It offers complete functionality for all Ethereym needs
  8. Extensive documentation
  9. It has a huge collection of test cases
  10. It has an MIT Licence.
If you are looking for another API to develop javascript with Ethereum, then you must consider Ether.js. It is loaded with features that any Blockchain developer would require. The library is designed in such a way that it matches the need of the client. With the use of ether.js, it becomes easier to write javascript-based wallets.
Light.js
The third entrant in our list is light.js. It provides high-level tools which are used for developing efficient Dapps on the light client. This is also a great alternative to web3.js. It works with remote nodes and makes it easy for a developer to build decentralized applications with ease.
Here it becomes important to mention that light.js chooses the best pattern which works with light clients, it listens to headers and makes API calls on a new header an ensures that network calls are not extreme.
The end objective is to put up a high-level library such that the decentralized app developers can make use of this and create apps.
Besides, these there are other APIs like Web3-wrapper can also be used by blockchain developer. These APIs aim to simplify the task of the developer so that they can create apps which work seamlessly.
Final Thoughts
If you are working on a decentralized application developed, then you would come across either of these apps or will be using one of them. In case you are new to this field and are looking for gaining comprehensive knowledge in this field, then you must go for a Certified Ethereum Expert online training program by Blockchain Council. This exhaustive program will help you learn about Ethereum, APIs and allied concepts and at the same time, learn how to use them. In case you want to learn how to use smart contracts on Ethereum based applications, then you must opt for Certified Solidity Developer coursesby Blockchain Council. Connect with us today to explore more about Ethereum.
submitted by Blockchain_org to BlockchainStartups [link] [comments]

Monthly Nano News: December 2019 + Year Recap Special

This is what NANO has been up to lately. I don't think I lie if I say it has been quite an amazing year!
See you soon and happy new year! Something nice is coming soon that I have been working on for a while, stay tuned..

December 2019

November 2019

October 2019

September 2019

August 2019

July 2019

June 2019

May 2019

Apr 2019

Mar 2019

Feb 2019

Jan 2019


More news here: https://nanolinks.info/news

https://preview.redd.it/9sw5nkoxlt741.png?width=749&format=png&auto=webp&s=3426d4eafb9430c0304a6d161596102536df4318
submitted by Joohansson to nanocurrency [link] [comments]

Using Bitcoin Cash to send and receive transactions and get balance in Vapor Swift server

I have a project in Ruby on Rails but it uses the accounts feature to transfer BCH/BTC between users and this is deprecated.
I saw the yenom/BitcoinKit project on GitHub and thought that is awesome, it even says I can send/receive and get the balance of HD Wallets. Then I read in "Issues" that's exactly the part that "might not be working".
Then I thought okay maybe I will use Bitcoin-ABC but the RPC is not documented?
Maybe BCHD, but it doesn't support SLP? The BCHWallet is separate project and uses a "single wallet" only.
There is some controversy with the miner infrastructure funding and the different Bitcoin Cash groups.
Is the obvious solution to try to use the top choice, Bitcoin-ABC and figure out the RPC commands? I just wanted to do transfers between HD wallets, or at the very least see the balance of an HD wallet using the master public key, and also to send transactions using some API.
Or should I use rest.bitcoin.com?
submitted by cacaosteve to btc [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]

Achain Galaxy Monthly Update | March 1–31, 2020

Achain Galaxy Monthly Update | March 1–31, 2020

Achain Monthly Report

Core Development:

1. Achain 2.0 Development Progress

  • Added the “nobid” effective mechanism. The Achain network can optionally specify account names that meet the rules when creating accounts.
  • Adjusted the contract test project to adapt to the new modification and it’s 20% complete.
  • Modified the in-progress flag when the peer connection is closed.
  • Added exception handling when facilitating the handshake messages to enhance code robustness.
  • Created the “Achain-exchange” project folder and added exchange docking documents.
  • Completed Achain 2.0 offline signature java version SDK and address a generation demo.
  • Completed Achain 2.0 RPC related serialization and deserialization java version SDK.
  • Studied the basic concepts and implementation details of the hot stuff consensus algorithm.
2. Achain 2.0 browser and peripheral development progress
  • Achain 2.0 Wallet, Windows version 2.0 (Chinese), is being developed, tested, and 40% completed.
  • Achain 2.0 Wallet Mac version 2.0 (Chinese), is being developed, tested, and 40% completed.
  • Achain 2.0 Wallet, Windows version 2.0 (English), is being developed and 60% completed.
  • Achain 2.0 Wallet, Mac version 2.0 (English), is being developed and 60% completed.

Community Management:

  • The first AMA event of the Achain Galaxy in 2020 was successfully held in the English telegram group on March 18. The founder Cui Meng responded to the questions raised by the overseas users about project technology, community, market, ecosystem. He also elaborated and prospected the future development of Achain Galaxy. To read the AMA please visit: https://medium.com/@AchainOfficial/achain-talks-ep06-a7b4a0376a9f
  • Achain founder Cui Meng revealed in AMA that the recently launched ATT project on Bithumb Global will soon become another important member of the Achain Galaxy and the first European project in the Achain Galaxy. Details will be announced.
  • ATT is a top-ranking project that offers decentralized information and communication protocols. ATT, a reserve member of the Achain Galaxy, was reported by well-known domestic blockchain media outlets: Golden Finance, Bihu, and Mars Finance. The article titles include, “Does this protocol direct the future?” “How blockchain + social network will perform in the arena of data interests? ATT Provides New Solutions. A Quick Understanding of the ATT Decentralized Information and Communication Protocol”. The articles discuss the future development direction of decentralized information and communication protocols.
  • The well-known foreign blockchain media Coinspeaker and Blockmanity released the news “ATT decentralized information communication protocol” “In the Arena of Data Interests, How Will Blockchain + Social Perform? ATT Offers a New Solution”. The article affirms the potential of ATT, a member of the Achain Galaxy.
  • The well-known exchange Bithumb Global and ATT, a reserve member of the Achain Galaxy, commenced large-scale publicity in South Korea for the ATT launch and excitement quickly escalated.
  • The Achain community congratulates Galaxy member ATT which launched on Bithumb Global, the world’s largest exchange. The ATT listing on Bithumb Global shows the mainstream market’s recognition of ATT, a member of the Achain Galaxy, which has greatly promoted the growth and development of the Achain Galaxy.
  • Alliance, a well-known Korean blockchain investment institution, is very optimistic about the future direction of ATT, a member of the Achain Galaxy. Achain has signed a strategic cooperation with ATT which gives strong funding support and will localize ATT within the Korean community and support comprehensive Korean public activities.
  • Achain member Eminer prepares for the upcoming Bitcoin halving which coincides with the wet weather season which lowers the electricity price from May. Eminer contacted the authorities in preparation for the anticipated water supply and is ready to leverage the wet season to strengthen their business.
  • Achain labs will work with SlowMist Technology to conduct a security audit of the core code of the Achain 2.0 mainnet to ensure its security and each of use.
  • The improvement of the Achain 2.0 contract system will allow global developers to contribute base code on the 2.0 mainnet to develop products that will compete with popular DeFi products such as Uniswap and compound protocols. Achain Capital will also focus on this area and priority investments will be available to develop solutions.
  • Achain Galaxy team selected 4 best user questions in the AMA and distributed rewards. We appreciate users that consistently provide support. For details please visit: https://twitter.com/AchainOfficial/status/1240637571677310976
submitted by yimo1985 to Achain_Official [link] [comments]

A welcome message to developers from Bitcoin.com's Developer Services lead, Gabriel Cardona.

Hi, my name is Gabriel, I lead Developer Services at bitcoin.com. We have a suite of developer tools which should be familiar to an ETH dev.
https://developer.bitcoin.com is the home of all our developer documentation
https://developer.bitcoin.com/bitbox/ is our typescript framework similar to truffle
https://developer.bitcoin.com/slp is for creating, minting, sending and burning tokens. It's also a superset of BITBOX SDK
rest.bitcoin.com - this is the json rpc over http
https://bitdb.bitcoin.com - real time indexer of BCH blockchain in to mongodb collections
https://bitsocket.bitcoin.com - bitbd data in real-time over websockets
https://slpdb.bitcoin.com - entire token graph in mongodb collections
https://slpsocket.bitcoin.com - slpdb data in real-time over websockets
Badger is our fork of MetaMask for BCH:
Cashscript is our smart-contract language inspired by Solidity. It exports an Arifact w/ ABI
CashScript examples as .cash files and needed typescript files to transpile and run them
Testnet Faucet
Any of the above cloud services also works w/ testnet by adding a t to the beginning of the url. For example https://trest.bitcoin.com
We have a developer discord and a telegram room.
I'm @cgcardona and I'm happy to help on-ramp in any way. Cheers 🎩
Source.
submitted by MemoryDealers to btc [link] [comments]

Bitcoin Verde v1.2.1 - 20191115 HF Support

Bitcoin Verde v1.2.1

https://github.com/SoftwareVerde/bitcoin-verde
What's new in v1.2.1:
If you're running a Bitcoin Verde node be sure to upgrade to the latest version before the 15th. And feel free to let me know you're running a node--it would be great to hear. Currently the resources required to run a node are quite large, so we don't expect there to be many until a subsequent release. Additionally, there have been some database changes since the last major release, but migration will be handled during the node's first restart. If you encounter any problems just send me a message, or find me in Telegram: https://t.me/bitcoinverde .
Notable upgrades for this patch is support for the 20191115 HF, which includes Schnorr signature support for multisig transactions.
Bitcoin Verde put a strong emphasis on SLP support this release which includes RPC commands for checking the validity of SLP transactions. SLP Transactions may be checked via the explorer's API or checked directly via RPC. You can refer to the scripts directory, or check the documentation at https://bitcoinverde.org/documentation/#rpc for more details.
What's coming in future releases:
We have added two custom network calls for SPV wallets to query the validity of SLP transactions. These calls are obviously trusted calls, and the network level is not encrypted, so they may be subject to man-in-the-middle attacks without special considerations. We're refining this feature and plan to release it in the next version of Bitcoin Verde.
We are also investing a lot of effort in improving the initial-block-download times of Bitcoin Verde. This feature involves a rather large database restructure, but has shown to improve performance of the IBD and synced validation significantly. Currently Bitcoin Verde stores, validates, and indexes transactions at a rate of ~2k-12k tx/s, depending on hardware, configuration, and mempool synchronization with the network. We expect to double this in a near-future release.
We've also been collaborating with Xavier Kral from bitcoin.com to reduce to disk footprint of Bitcoin Verde via both hardening "trim" mode and changing the way some data is stored within the database without losing existing functionality.
As always, we're proud to be a part of the Bitcoin Cash community, and love collaborating with brilliant people like Mark Lundeburg, Josh Ellithorpe, Amaury Séchet, and many many others.
submitted by FerriestaPatronum to btc [link] [comments]

Bitcoin Unlimited 1.6.0.1 has just been released

Download the latest release of Bitcoin Unlimited (1.6.0.1, July 19th, 2019) from:
 
https://www.bitcoinunlimited.info/download
 
This is a a bug fix release candidate of Bitcoin Unlimited compatible with the Bitcoin Cash protocol.
This is list of the main changes that have been merged in this release:
 
Release notes: https://github.com/BitcoinUnlimited/BitcoinUnlimited/blob/dev/doc/release-notes/release-notes-bucash1.6.0.1.md
 
PS Ubuntu PPA repository is currently being updated to serve for BUcash 1.6.0.1.
submitted by s1ckpig to btc [link] [comments]

Bitcoin Unlimited - Bitcoin Cash edition 1.6.0.0 has just been released

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

[FOR HIRE] Python Software Engineer — 12 years of experience

Looking for a job: CTO, Team Lead, Developer. 12 years of professional experience in software development. Python, JavaScript. Available for remote work and relocation.
Experienced in planning the development of new projects, working on the architecture, preparing the requirements, writing specifications, and leading teams. I enjoy teaching people to code and doing code review. I ask other developers to write code of high quality and refactor it so the code is simple and readable.
Worked on 20 complex projects for companies from 5 countries, including an adaptive online learning platform for Bloomberg and The Economist used by students around the world for exam preparation.
I have experience with caching, task queues, unit tests, image processing, encoding, API, parsing, multithreaded and asynchronous applications.
When working on a project, I write detailed documentation that helps any new developers to quickly join the project.
[email protected]
submitted by aruseni to RemoteJobs [link] [comments]

[FOR HIRE] Python Software Engineer — 12 years of experience

Looking for a job: CTO, Team Lead, Developer. 12 years of professional experience in software development. Python, JavaScript. Available for remote work and relocation.
Experienced in planning the development of new projects, working on the architecture, preparing the requirements, writing specifications, and leading teams. I enjoy teaching people to code and doing code review. I ask other developers to write code of high quality and refactor it so the code is simple and readable.
Worked on 20 complex projects for companies from 5 countries, including an adaptive online learning platform for Bloomberg and The Economist used by students around the world for exam preparation.
I have experience with caching, task queues, unit tests, image processing, encoding, API, parsing, multithreaded and asynchronous applications.
When working on a project, I write detailed documentation that helps any new developers to quickly join the project.
[email protected]
submitted by aruseni to Jobs4Bitcoins [link] [comments]

Bitcoin JSON RPC API (bitcoin-cli) in your web browser! [new launch for core 0.18.0]

Very excited to announce the all-new https://ChainQuery.com
Entirely up to date with Bitcoin Core 0.18.0 and sporting sexy new navigation, advanced search, category filtering, and a great new UI.
ChainQuery includes full documentation on all 140 Bitcoin RPCs along with the unique ability to run commands in your browser for 27 commands and growing.
Bitcoin core 0.18.0 included a significant RPC update outlined below:
New RPCs added in 0.18.0:
Updated RPC's in 0.18.0:
Deprecated RPCs in 0.18.0:
All depecated RPC's from 0.18.0 onward can be found here: https://chainquery.com/bitcoin-cli#deprecated
Check it out and let me know what you think!
submitted by CoinCadence to Bitcoin [link] [comments]

[FOR HIRE] Python Software Engineer — 12 years of experience

Looking for a job: CTO, Team Lead, Developer. 12 years of professional experience in software development. Python, JavaScript. Available for remote work and relocation.
Experienced in planning the development of new projects, working on the architecture, preparing the requirements, writing specifications, and leading teams. I enjoy teaching people to code and doing code review. I ask other developers to write code of high quality and refactor it so the code is simple and readable.
Worked on 20 complex projects for companies from 5 countries, including an adaptive online learning platform for Bloomberg and The Economist used by students around the world for exam preparation.
I have experience with caching, task queues, unit tests, image processing, encoding, API, parsing, multithreaded and asynchronous applications.
When working on a project, I write detailed documentation that helps any new developers to quickly join the project.
[email protected]
submitted by aruseni to jobpostings [link] [comments]

Bitcoin Unlimited 1.6.0.1 has just been released

Download the latest release of Bitcoin Unlimited (1.6.0.1, July 19th, 2019) from:
 
https://www.bitcoinunlimited.info/download
 
This is a a bug fix release candidate of Bitcoin Unlimited compatible with the Bitcoin Cash protocol.
This is list of the main changes that have been merged in this release:
 
Release notes: https://github.com/BitcoinUnlimited/BitcoinUnlimited/blob/dev/doc/release-notes/release-notes-bucash1.6.0.1.md
 
PS Ubuntu PPA repository is currently being updated to serve for BUcash 1.6.0.1.
submitted by s1ckpig to Bitcoincash [link] [comments]

Accepting Dogecoin Payments

Hi! I had a cool idea for a project using dogecoin but I was curious of the best+quickest way to accept payments in dogecoin while making sure that they are legitimate. I was also sort of curious if it was a bad idea to do fractions of dogecoins and if there is any benefit to larger transactions (e.g. 5 doge in one transaction vs 1 doge in 5 transactions). I just want to make sure the project won't hurt the network!
submitted by mstrodl123 to dogecoin [link] [comments]

⚡ Lightning Network Megathread ⚡

Last updated 2018-01-29
This post is a collaboration with the Bitcoin community to create a one-stop source for Lightning Network information.
There are still questions in the FAQ that are unanswered, if you know the answer and can provide a source please do so!

⚡What is the Lightning Network? ⚡

Explanations:

Image Explanations:

Specifications / White Papers

Videos

Lightning Network Experts on Reddit

  • starkbot - (Elizabeth Stark - Lightning Labs)
  • roasbeef - (Olaoluwa Osuntokun - Lightning Labs)
  • stile65 - (Alex Akselrod - Lightning Labs)
  • cfromknecht - (Conner Fromknecht - Lightning Labs)
  • RustyReddit - (Rusty Russell - Blockstream)
  • cdecker - (Christian Decker - Blockstream)
  • Dryja - (Tadge Dryja - Digital Currency Initiative)
  • josephpoon - (Joseph Poon)
  • fdrn - (Fabrice Drouin - ACINQ )
  • pmpadiou - (Pierre-Marie Padiou - ACINQ)

Lightning Network Experts on Twitter

  • @starkness - (Elizabeth Stark - Lightning Labs)
  • @roasbeef - (Olaoluwa Osuntokun - Lightning Labs)
  • @stile65 - (Alex Akselrod - Lightning Labs)
  • @bitconner - (Conner Fromknecht - Lightning Labs)
  • @johanth - (Johan Halseth - Lightning Labs)
  • @bvu - (Bryan Vu - Lightning Labs)
  • @rusty_twit - (Rusty Russell - Blockstream)
  • @snyke - (Christian Decker - Blockstream)
  • @JackMallers - (Jack Mallers - Zap)
  • @tdryja - (Tadge Dryja - Digital Currency Initiative)
  • @jcp - (Joseph Poon)
  • @alexbosworth - (Alex Bosworth - yalls.org)

Medium Posts

Learning Resources

Books

Desktop Interfaces

Web Interfaces

Tutorials and resources

Lightning on Testnet

Lightning Wallets

Place a testnet transaction

Altcoin Trading using Lightning

  • ZigZag - Disclaimer You must trust ZigZag to send to Target Address

Lightning on Mainnet

Warning - Testing should be done on Testnet

Atomic Swaps

Developer Documentation and Resources

Lightning implementations

  • LND - Lightning Network Daemon (Golang)
  • eclair - A Scala implementation of the Lightning Network (Scala)
  • c-lightning - A Lightning Network implementation in C
  • lit - Lightning Network node software (Golang)
  • lightning-onion - Onion Routed Micropayments for the Lightning Network (Golang)
  • lightning-integration - Lightning Integration Testing Framework
  • ptarmigan - C++ BOLT-Compliant Lightning Network Implementation [Incomplete]

Libraries

Lightning Network Visualizers/Explorers

Testnet

Mainnet

Payment Processors

  • BTCPay - Next stable version will include Lightning Network

Community

Slack

IRC

Slack Channel

Discord Channel

Miscellaneous

⚡ Lightning FAQs ⚡

If you can answer please PM me and include source if possible. Feel free to help keep these answers up to date and as brief but correct as possible
Is Lightning Bitcoin?
Yes. You pick a peer and after some setup, create a bitcoin transaction to fund the lightning channel; it’ll then take another transaction to close it and release your funds. You and your peer always hold a bitcoin transaction to get your funds whenever you want: just broadcast to the blockchain like normal. In other words, you and your peer create a shared account, and then use Lightning to securely negotiate who gets how much from that shared account, without waiting for the bitcoin blockchain.
Is the Lightning Network open source?
Yes, Lightning is open source. Anyone can review the code (in the same way as the bitcoin code)
Who owns and controls the Lightning Network?
Similar to the bitcoin network, no one will ever own or control the Lightning Network. The code is open source and free for anyone to download and review. Anyone can run a node and be part of the network.
I’ve heard that Lightning transactions are happening “off-chain”…Does that mean that my bitcoin will be removed from the blockchain?
No, your bitcoin will never leave the blockchain. Instead your bitcoin will be held in a multi-signature address as long as your channel stays open. When the channel is closed; the final transaction will be added to the blockchain. “Off-chain” is not a perfect term, but it is used due to the fact that the transfer of ownership is no longer reflected on the blockchain until the channel is closed.
Do I need a constant connection to run a lightning node?
Not necessarily,
Example: A and B have a channel. 1 BTC each. A sends B 0.5 BTC. B sends back 0.25 BTC. Balance should be A = 0.75, B = 1.25. If A gets disconnected, B can publish the first Tx where the balance was A = 0.5 and B = 1.5. If the node B does in fact attempt to cheat by publishing an old state (such as the A=0.5 and B=1.5 state), this cheat can then be detected on-chain and used to steal the cheaters funds, i.e., A can see the closing transaction, notice it's an old one and grab all funds in the channel (A=2, B=0). The time that A has in order to react to the cheating counterparty is given by the CheckLockTimeVerify (CLTV) in the cheating transaction, which is adjustable. So if A foresees that it'll be able to check in about once every 24 hours it'll require that the CLTV is at least that large, if it's once a week then that's fine too. You definitely do not need to be online and watching the chain 24/7, just make sure to check in once in a while before the CLTV expires. Alternatively you can outsource the watch duties, in order to keep the CLTV timeouts low. This can be achieved both with trusted third parties or untrusted ones (watchtowers). In the case of a unilateral close, e.g., you just go offline and never come back, the other endpoint will have to wait for that timeout to expire to get its funds back. So peers might not accept channels with extremely high CLTV timeouts. -- Source
What Are Lightning’s Advantages?
Tiny payments are possible: since fees are proportional to the payment amount, you can pay a fraction of a cent; accounting is even done in thousandths of a satoshi. Payments are settled instantly: the money is sent in the time it takes to cross the network to your destination and back, typically a fraction of a second.
Does Lightning require Segregated Witness?
Yes, but not in theory. You could make a poorer lightning network without it, which has higher risks when establishing channels (you might have to wait a month if things go wrong!), has limited channel lifetime, longer minimum payment expiry times on each hop, is less efficient and has less robust outsourcing. The entire spec as written today assumes segregated witness, as it solves all these problems.
Can I Send Funds From Lightning to a Normal Bitcoin Address?
No, for now. For the first version of the protocol, if you wanted to send a normal bitcoin transaction using your channel, you have to close it, send the funds, then reopen the channel (3 transactions). In future versions, you and your peer would agree to spend out of your lightning channel funds just like a normal bitcoin payment, allowing you to use your lightning wallet like a normal bitcoin wallet.
Can I Make Money Running a Lightning Node?
Not really. Anyone can set up a node, and so it’s a race to the bottom on fees. In practice, we may see the network use a nominal fee and not change very much, which only provides an incremental incentive to route on a node you’re going to use yourself, and not enough to run one merely for fees. Having clients use criteria other than fees (e.g. randomness, diversity) in route selection will also help this.
What is the release date for Lightning on Mainnet?
Lightning is already being tested on the Mainnet Twitter Link but as for a specific date, Jameson Lopp says it best
Would there be any KYC/AML issues with certain nodes?
Nope, because there is no custody ever involved. It's just like forwarding packets. -- Source
What is the delay time for the recipient of a transaction receiving confirmation?
Furthermore, the Lightning Network scales not with the transaction throughput of the underlying blockchain, but with modern data processing and latency limits - payments can be made nearly as quickly as packets can be sent. -- Source
How does the lightning network prevent centralization?
Bitcoin Stack Exchange Answer
What are Channel Factories and how do they work?
Bitcoin Stack Exchange Answer
How does the Lightning network work in simple terms?
Bitcoin Stack Exchange Answer
How are paths found in Lightning Network?
Bitcoin Stack Exchange Answer
How would the lightning network work between exchanges?
Each exchange will get to decide and need to implement the software into their system, but some ideas have been outlined here: Google Doc - Lightning Exchanges
Note that by virtue of the usual benefits of cost-less, instantaneous transactions, lightning will make arbitrage between exchanges much more efficient and thus lead to consistent pricing across exchange that adopt it. -- Source
How do lightning nodes find other lightning nodes?
Stack Exchange Answer
Does every user need to store the state of the complete Lightning Network?
According to Rusty's calculations we should be able to store 1 million nodes in about 100 MB, so that should work even for mobile phones. Beyond that we have some proposals ready to lighten the load on endpoints, but we'll cross that bridge when we get there. -- Source
Would I need to download the complete state every time I open the App and make a payment?
No you'd remember the information from the last time you started the app and only sync the differences. This is not yet implemented, but it shouldn't be too hard to get a preliminary protocol working if that turns out to be a problem. -- Source
What needs to happen for the Lightning Network to be deployed and what can I do as a user to help?
Lightning is based on participants in the network running lightning node software that enables them to interact with other nodes. This does not require being a full bitcoin node, but you will have to run "lnd", "eclair", or one of the other node softwares listed above.
All lightning wallets have node software integrated into them, because that is necessary to create payment channels and conduct payments on the network, but you can also intentionally run lnd or similar for public benefit - e.g. you can hold open payment channels or channels with higher volume, than you need for your own transactions. You would be compensated in modest fees by those who transact across your node with multi-hop payments. -- Source
Is there anyway for someone who isn't a developer to meaningfully contribute?
Sure, you can help write up educational material. You can learn and read more about the tech at http://dev.lightning.community/resources. You can test the various desktop and mobile apps out there (Lightning Desktop, Zap, Eclair apps). -- Source
Do I need to be a miner to be a Lightning Network node?
No -- Source
Do I need to run a full Bitcoin node to run a lightning node?
lit doesn't depend on having your own full node -- it automatically connects to full nodes on the network. -- Source
LND uses a light client mode, so it doesn't require a full node. The name of the light client it uses is called neutrino
How does the lightning network stop "Cheating" (Someone broadcasting an old transaction)?
Upon opening a channel, the two endpoints first agree on a reserve value, below which the channel balance may not drop. This is to make sure that both endpoints always have some skin in the game as rustyreddit puts it :-)
For a cheat to become worth it, the opponent has to be absolutely sure that you cannot retaliate against him during the timeout. So he has to make sure you never ever get network connectivity during that time. Having someone else also watching for channel closures and notifying you, or releasing a canned retaliation, makes this even harder for the attacker. This is because if he misjudged you being truly offline you can retaliate by grabbing all of its funds. Spotty connections, DDoS, and similar will not provide the attacker the necessary guarantees to make cheating worthwhile. Any form of uncertainty about your online status acts as a deterrent to the other endpoint. -- Source
How many times would someone need to open and close their lightning channels?
You typically want to have more than one channel open at any given time for redundancy's sake. And we imagine open and close will probably be automated for the most part. In fact we already have a feature in LND called autopilot that can automatically open channels for a user.
Frequency will depend whether the funds are needed on-chain or more useful on LN. -- Source
Will the lightning network reduce BTC Liquidity due to "locking-up" funds in channels?
Stack Exchange Answer
Can the Lightning Network work on any other cryptocurrency? How?
Stack Exchange Answer
When setting up a Lightning Network Node are fees set for the entire node, or each channel when opened?
You don't really set up a "node" in the sense that anyone with more than one channel can automatically be a node and route payments. Fees on LN can be set by the node, and can change dynamically on the network. -- Source
Can Lightning routing fees be changed dynamically, without closing channels?
Yes but it has to be implemented in the Lightning software being used. -- Source
How can you make sure that there will be routes with large enough balances to handle transactions?
You won't have to do anything. With autopilot enabled, it'll automatically open and close channels based on the availability of the network. -- Source
How does the Lightning Network stop flooding nodes (DDoS) with micro transactions? Is this even an issue?
Stack Exchange Answer

Unanswered Questions

How do on-chain fees work when opening and closing channels? Who pays the fee?
How does the Lightning Network work for mobile users?
What are the best practices for securing a lightning node?
What is a lightning "hub"?
How does lightning handle cross chain (Atomic) swaps?

Special Thanks and Notes

  • Many links found from awesome-lightning-network github
  • Everyone who submitted a question or concern!
  • I'm continuing to format for an easier Mobile experience!
submitted by codedaway to Bitcoin [link] [comments]

Logs of yesterday's dev meeting

 Dev meeting?  Would say so, yes  The people are still exhausted from the payment ID meeting :)  Guess we could ping some people  vtnerd, moneromooo, hyc, gingeropolous, TheCharlatan, sarang, suraeNoether, jtgrassie  Anyone up for a meeting?  Yep I'm here  Here  o/  Perhaps we should just start and people will eventually hop in?   oof   sorry guys, I'm working on the new FFS and I forgot all about this. Got a couple of new volunteers.   This literally might be able to launch tomorrow.  I know that. It's called "flow" :)  I could run if you're out of time?   go for it dEBRUYNE   you guys are going to like this new FFS. We're like 99% done.  Hi  rehrar: someone else do the milestone thing already?  All right, jtgrassie, perhaps you'd to start w/ briefly describing your most recent PR? https://github.com/monero-project/monero/pull/5091   oneiric, xiphon did everything   like....everything  As far as I can see, it allows the user to push his transaction over I2P, thereby masking the origin IP of the sendeuser  great  And it hooks into vtnerd's PR right?  Sure. It basically just builds on vtnerds Tor stuff.  sorry dEBRUYNE  Really not much added.  I have it running and tested.  From the perspective of the user, what needs to be configured exactly?  Nice  Assuming the PR is included in the release binaries  I'm using knacccs i2p-zero duirng testing but will of course work with any i2p setup   sorry dEBRUYNE <= Np  Looks a little like dams breaking, now that we have some dark clouds over Kovri and people take matters into their own hands ...  User needs to run i2p, expose a socks service and and inbound tunnel.  Basically same as Tor  Okay, so should be reasonable as long as we write proper documentation for it (e.g. an elaborate guide)  rbrunner, yes, knaccc credit for jumping on i2p-zero really  dEBRUYNE: documentation monero side is kindof done. i2p side is very much implementation specific.  I suppose we could write some guides for the most popular implementations?  e.g. i2p-zero aims to be zero conf, but i2pd or Kovri would be differnet.  I see, great  vtnerd___: Do you want to add anything?  could amend the current kovri guide for monero use from --exclusive-peer to the new proxy support  Now I have i2p-zero running and tested with the #5091, I plan to jump back over to helping knaccc on getting that polished.  I added support for socks proxy in the basic wallets  ^ excellent  Yes vtnerd___ I havent tested it yet but looks sweet.  So connections to `monerod` over Toi2p are possible within wallet cli and wallet rpc  Awesome  This also implies auth+encryption even if ssl is not in use (when using an onion or i2p address)  All right  moneromooo: are you here? If so, could you perhaps share what you've been working on?  I am.  I revived the SSL PR, more stuff on multi sender txes, an implementation of ArticMine's new block size algorithm.  I presume a multi sender tx works similar to multisig insofar as the senders have to exchange data before the transaction can be performed right?  Yes.  There are 2 SSL PRs. What's the diff?  Theoretically this would also allow the sender to provide an output right? Which would be kind of similar to Bitcoin's P2EP  The second one adds some things like selecting a cert by fingerprint.  Yes.  (for the first sentence)  All right, awesome  For anyone reading, this breaks the assumption of the inputs belonging to a single sender, which makes analysis more difficult  Nice side-effect.  Much work coming for the various wallets to support that  rbrunner: Anything you'd like to share in the meeting btw?  Yes, just a little info  I have started to seriously investigate what it would mean to integrate Monero into OpenBazaar  I have already talked with 2 of their devs, was very interesting  In maybe 2 or 3 weeks I intend to write a report  Too early to tell much more :)  Soon^tm I guess :)  Yep  Currently wrestling with Go debugging  whole new world  moneromooo: Has pony recently shared any insights regarding the upcoming 0.14 release btw?  No.  All right  I would love to see the tor & i2p PR's merged sooner rather than later so we can get more testing done.  ^ +1  Isn't that famous early code freeze already on the horizon?  fluffypony, luigi1111 ^  I suppose I could provide a little update regarding the GUI btw  As always, lots of bug fixes and improvements :-P  selsta has recently added a feature to support multi accounts  dsc_ has revamped the wizard and will now start working on implementing the different modes and a white theme  dsc_ is working fulltime on the GUI already?  yes  :)   dsc_ is bae  In light of the recent payment ID discussion, we've also, by default, disabled the option to add a payment ID unless the user explicitely activates the option on the settings page  rehrar ^  nice   I spoke about this yesterday at the coffee chat, this is not a good decision.  How does it handle integrated addresses? The same way?  rehrar ?   For the next many months, we are still stuck with PAyment IDs in the ecosystem. Making it harder for people to access them will make Monero suck so hard to use for the average person for many months.  i agree with rehrar   Remove the option of Payment IDs when we remove Payment IDs  rehrar: The new GUI release won't be live until probably mid march though  Which is a few weeks in advance of the scheduled protocol upgrade   Payment ID removal comes in October   right, but Payment IDs are not removed in March  Did we not have loose consensus on removing the old, unencrypted payment IDs in march?   they are removed in October  We had discussed a deprecation in March  and a ban in October   ok, then if we are going to do that, we have to commit to it and contact the exchanges like Binance that use them and get rid of them in the next few months  (of unencrypted)   Binance is huge, and if they still use them, then people will be very upset that they can't deposit or use Payment IDs easily   I'm just speaking from a UX perspective.  I thought it was unencrypted in April and possibly encrypted in October  Yes I do agree  Timeline and notes: https://github.com/monero-project/meta/issues/299  impossible to remove them for march, many exchanges still use them  We can defer it to the 0.15 release if needed  Well, that wasn't the impression for them log that I just read today  This was all discussed in the earlier meeting linked above   We have to force the ecosystem off of Payment IDs before we remove them from the UI, is all I'm saying  Remove != make difficult to use  ... or make them more difficult there, right?  ping sgp_   sarang, I understand, and I agreed with you during that meeting. But then I started thinking of it as a UX person, which I am.   And that huge massive problem leapt out at me  i think making them difficult to generate is a good idea but making them difficult to consume and use is a bad idea  well, maybe not a good idea, but a better idea   ^  If we defer the decision to depriciate long payment IDs to october, won't we have the same issue then?  The UI can gave an expandable payment ID field like MyMonero and we can still call it deprecated   It is foolhardy to remove an option that the ecosystem uses. So I suggest we keep the Payment ID in the UI until October when they are completely banned.   no dEBRYUNE, because they will be banned via consensus  sgp_ imo it may be a misdirection of dev resources to add that since things are proceeding in the short term rather than long term  but this is a relatively minor point  Nothing matters til exchanges change  All right   The issue is that consensus will still have them in April, and exchanges won't upgrade because they are still allowed. Thus they must still be in the UI.  endogenic these changes are already merged in the GUI to hide it like you do  ok   But when they are banned, exchanges are forced to upgrade or stop using Monero, so we can remove them safely because they won't be in use  rehrar: that's a strong assumption   sarang that they will upgrade?  yes   if they don't, then they can't use Monero  If exchanges require pid, users need a way to set a pid. Making it hard for the user in the interim is just going to be a nightmare.   we have decided to take our "stand" in October  A way that is not too hard, then  To be clear, we still intend to deprecate long encrypted payment IDs in April right? But no enforcement until October   the term "deprecated" doesn't mean much if it's still allowed, and used in popular places   yes, as far as I understand it   jtgrassie, exactly  True I suppose  dEBRUYNE: we need to be more specific when talking about deprecation   the person who suffers is the user  There are two proposals for GUI deprecation:  1. Hide it in the send screen with a simple option to expand (currently merged iirc)  2. Hide it completely in the send screen unless users enable the field in advanced settings (PR'd but not merged yet iirc)  What are the arguments for 2?   Both are poor options, but 1 is better than 2 by a long shot   Well the people who need to be made to "suffer" are the exchanges. And I don't see a way to make exchanges "suffer" other than by having their suffering customers complain to them constantly that they need to update.  ^  CLI has something similar where users need to set a manual payment ID transfer mode. Not sure if it's merged yet   the way to make the exchanges suffer is when we ban PIDs. They either upgrade or don't use Monero.  exact;y  Agree with rerahr here  have exchanges been provided with clear, practical, sufficient technical upgrade plans for supporting what they're doing with PIDs but with subaddrs?    Both are poor options, but 1 is better than 2 by a long shot <= I wouldn't call 1. a poor option. Have you actually checked how it looks?  Because it states "Payment ID" and a user has to click on the + to expand the field  endogenic: yes the email when out. Blog post coming soon, but contains the same info as the email  also the exhcnages' users are often using wallets that don't support subaddresses  ok great   as well, it should be noted that the timeline for exchanges to upgrade is September, not October when the fork is.  Which wallets are that?  Rehrar: I don't see option 1. causing any issues/confusion  i guess it doesnt matter too much if withdrawing as a personal user the main address should suffice   Because September is when the new versions will be coming out without PIDs in the UI  If there's opposition to 2, 1 is fine. We can still call it deprecated which is the optics we need anyway   exchange users are often just using other exchanges lol. No wallets involved.   dsc_ dEBRUYNE, ok, I trust you guys here then  rbrunner: i was thinking mymonero last i heard  Ok  pigeons: rbrunner yes receiving on subaddresses won't be supported yet  sending to them has been possible though  and yes as learnandlurkin says often they withdraw to other systems like exhcnages that also dont yet support subaddresses  I really can't come up with any good argument for 2. right now  endogenic: seems not much of an issue then. Exchanges will typically support withdrawals to both subaddresses and plain addresses (especially if we are going to force them to use subaddresses)  For deposits, MyMonero works properly if the user sends to a subaddress  Actually the second solution was already merged: https://github.com/monero-project/monero-gui/pull/1866  Maybe not enough eyes watching :)   The important thing is to have done something to justify having a big "DEPRECATED IN APRIL" stamp on PIDs to spook exchanges in the interim  This was for solution 1: https://github.com/monero-project/monero-gui/pull/1855   The Monero Community Workgroup will start making noise everywhere we can to exchanges, and everywhere else that will listen. Try to get on those garbage news sites also.   So everyone knows that deprecated in April, and banned in September  Hey, for solution 1, write "Payment ID (optional, deprecated)" or similar there  rbrunner: noted  rehrar: probably wait until the blog post, but it should only be a few days   Maybe a Reddit sticky post would be useful?   With the blog post   If people are over freaking out about the hashrate  or terabyte blockchain :)  sigh  Any questions for the MRL side?  Is someone checking ArticMine's block size changes for weird behaviour in some cases etc ?  How would such testing work? Private blockchain?  I'm waiting on cost information from ArticMine to complete the model  Or just simulations?  Also, smooth suggested a mean rather than median for the 100000 block op. It would indeed be much nicer if it doesn't make the change worse.  You mean computationally or what?  Nicer ? Yes.  no sorting needed for mean  I'll add a separate sim for that  Well, just nicer. Forger the much.  Forger the Much sounds like the formal name of a Lord of the Rings character  :)  To close the payment ID discussion, in essence, we agree that we shouldn't make it difficult for the user to add a payment ID right (until 0.15 is released)  ?  I don't. I did make it harder.  In the CLI, somewhat other story, I would say  than the GUI  People there are used to juggle with options and CL parameters  rehrar: I recommend opening another issue to reverse 1866 and we can gather feedback on it there  Sounds good, to me at least   Dudes, if I do a Jitsi stream right now to show the new FFS in action, would you guys be interested in watching it?  I'd watch it, if the meeting is formally done  sure  yeah, can I start one and record it?   I'll give it in like fifteen minutes   I'll let you all know, stand by  I have a question on tx_extra if no one else has anything to talk about  People have said you can put arbitrary data in there in whatever format you want as long as you're willing to pay for it. However, do you need to mine the transaction for it to be included? I didn't think nodes would block transactions with arbitrary tx_extra data  It'll be in nodes' txpool when you relay it. A wallet could see it before it's mined.  moneromooo: will it be mined though?  by others  Is it valid ?  assume it's otherwise valid  Does it have a high enough fee ?  assume it does yes  I ran into conflicting information here: https://monero.stackexchange.com/a/3627/42  Then it will probably be mined.  I once had the idea to put "my" MMS messages in there, looked at the code, and found no hard blocks for tx_extra data  That answer looks incorrect.  It is incorrect  If it will be mined, then that meets my assumption. There seems to be some misconception that people will not mine transactions with arbitrary tx_extra. I can add some comments there  And please don't spam it, and don't put fingerprintable stuff in it. It's meant to be here for *useful* stuff that's "uniform" enough.  It will be mined, whether a wallet *displays* the tx_extra is a different question.  I don't think any wallet currently displays that  it soes if its a pid  I think  Yeah, of course :)  Great, that answers my question 
submitted by dEBRUYNE_1 to Monero [link] [comments]

KYC-Tezos wallets vulnerable to "blind sig" attack

KYC-Tezos wallets vulnerable to
Summary
Most KYC-Tezos wallets we tested are vulnerable to a simple yet catastrophic attack that can lead to loss of all funds on wallet (blind signature vulnerability). These wallets connect to a server (the RPC node) but they do not build the raw tx like normal cryptocurrency wallets, nor do they check the binary provided by the RPC before signing it. Should the RPC get hacked (or turn malicious) it will provide clients a malicious tx to sign: with no way to parse the binary, the unsuspecting user will sign a tx which sends 100% of their funds to the attacker's address. (Update: since publishing this post some wallets have fixed the issue, see table below)

Ledger
Ledger users are not safe. This video shows how funds can be stolen from a Ledger device.

Demo
To demonstrate the vulnerability we also expose a malicious RPC to test your wallet against it (warning: funds could be lost).


Vulnerable wallets

RPC address WHOIS record Can set custom RPC? Vulnerable?
Atomic n/a n/a No Yes
Galleon tezos-prod.cryptonomic-infra.tech Anonymous (Panama) Yes No (fixed in 0.7.0b+)
Guarda mainnet.tezrpc.me Anonymous (US) No Yes
Kukai mainnet.tezrpc.me Anonymous (US) No No
Librebox mainnet.tezrpc.me Anonymous (US) Yes No
Magnum tezos.mgnm.rocks (updated) Anonymous (Russia) No No (fixed in v137+)
T3Wallet n/a n/a No Yes
Tezbox Web mainnet.tezrpc.me Anonymous (US) Yes No (fixed)
Tezbox Chrome mainnet.tezrpc.me Anonymous (US) Yes No (fixed in 13.0.0)
Tezbox MacOs mainnet.tezrpc.me Anonymous (US) Yes No (fixed in 4.0.0+)
Tezbox Windows mainnet.tezrpc.me Anonymous (US) Yes No (fixed in 4.0.0+)
Tezos Blue n/a n/a No No (fixed in v0.4.3+)
TezBridge mainnet.tezbridge.com Anonymous (Panama) Yes Yes
WeTez n/a n/a No Yes

Why it matters
Cryptocurrency wallets were meant to be trustless, but most KYC-Tezos wallets are not. When you're signing any tx with these wallets you're trusting the server (RPC) to send your money where you actually want it to go. Even if you trust the sourcecode of your wallet and are not using a web wallet, you're still vulnerable. The RPC you rely upon could turn malicious (e.g. be hacked) at any moment in time, with no way for you to detect it.

How the attack works
  1. RPC turns malicious (e.g. gets hacked)
  2. Wallet securely connects to malicious RPC via HTTPS
  3. Wallet provides JSON of tx to build
  4. RPC provides malicious binary sending funds to attacker's address
  5. Wallet blindly signs binary
  6. RPC broadcasts tx: funds are now lost

In a variant of the attack, the unsuspecting user will set a malicious RPC as custom RPC in their wallet. There are multiple ways someone could be tricked to do that (see Electrum hack below).

Causes
More than wallet developers themselves, we deem KYC-Tezos developers inadequacy and lack of understanding of an adversarial environment as the culprit for this simple yet potentially catastrophic vulnerability.
1.Wrong design
The RPC exposes a JSON API to build the tx, which is then provided to the client for signing, and returned to the RPC for broadcast. This is not how a blockchain wallet should work: txs should be built and signed locally, and only then pushed to a server.
2.OCaml binary with no serialization specs
In the KYC-Tezos APIs there is no spec for the transaction binary format. tezos-data-encoding is the library responsible for encoding a tx, so the tx format is tightly coupled with the the serialization of OCaml objects. An OCaml binary with no spec is what led GUI wallet developers, who are not using OCaml, to just trust the binary provided by the RPC instead of parsing and checking it.

A secure channel with your attacker
SSL security between client and server won't help: if the RPC turns malicious, it will first establish a secure connection as usual and then provide a malicious tx to sign. Hiding in plain sight, KYC-Tezos APIs actually hint [1] to the vulnerability. The "solution" they suggest is securing the connection, which as already explained does not solve the issue at all while providing users a false sense of security.

Hiding in plain sight: a hint from KYC-Tezos APIs

What happened to Electrum
Recently more than $750,000 were stolen by an attacker spawning malicious Electrum servers and stealing BTC from Electrum users. [2][3]
The attack succeeded despite Electrum being way more secure than KYC-Tezos wallets: with Electrum the tx is generated by the client and not by the server.

Malicious RPC demo
Set this custom RPC in your wallet to test the vulnerability:
https://demo.tzlibre.io/malicious/ 
WARNING: IF YOUR WALLET IS VULNERABLE FUNDS WILL BE LOST AND SENT TO FOUNDATION BAKER 1 (tz3RDC3Jdn4j15J7bBHZd29EUee9gVB1CxD9)
As safety measure this demo RPC only manipulates recpient's address, and not the transaction amount as well.
If your wallet is vulnerable and not listed above yet, please let us know.

How we fixed it
We fixed the vulnerability in LibreBox by checking portions of the tx (such as destination address, amount, etc) after a reverse-engineering of the tx format itself.

Suggested next steps
  • KYC-Tezos users: do not sign any tx with a vulnerable wallet until the vulnerability is addressed.
  • Wallet developers: immediately start warning your users of the danger, until binary txs are parsed and checked. If you resolved the issue or if your wallet is not listed, feel free to contact us to update this post.
  • Tezos Foundation: immediately release specs for the binary tx format, and improve documentation to a more decent standard.

Update (1/14/2019): in a previous version of this post Kukai was wrongly listed as vulnerable. Kukai has never been vulnerable to the attack. Tezbox Web has fixed the vulnerability, while Tezbox Chrome, Tezbox MacOs, Tezbox Windows remain vulnerable.
Update (1/15/2019): Magnum has fixed the vulnerability in v137 and changed the RPC from mainnet.tezrpc.me to tezos.mgnm.rocks
Update (1/16/2019): Tezos Blue has fixed the vulnerability on Github [4], but their 3 apps remain vulnerable to date.
Update (1/17/2019): TezBox has fixed the vulnerability on Chrome, MacOs, Windows. Tezos Blue has fixed the vulnerability on all 3 apps with v0.4.3
Update (1/18/19); Galleon has fixed the vulnerability in version 0.7.0b

References
[1] https://tezos.gitlab.io/alphanet/introduction/various.html#signer
[2] https://github.com/spesmilo/electrum/issues/4968
[3] https://www.zdnet.com/article/users-report-losing-bitcoin-in-clever-hack-of-electrum-wallets/
[4] https://github.com/tezos-blue/client/commit/7eb335df64f4b72706fa2252dd369edca903ee93
submitted by tzlibre to tzlibre [link] [comments]

Bitcoin JSON-RPC Tutorial 4 - Command Line Interface Bitcoin JSON-RPC Tutorial 1 Bitcoin JSON-RPC Tutorial 1 Programming Bitcoin-qt using the RPC api (1 of 6) Bitcoin JSON-RPC Tutorial 5 - Your First Calls

A full disclosure of the impact of CVE-2018-17144, a fix for which was released on September 18th in Bitcoin Core versions 0.16.3 and 0.17.0RC4. Bitcoin Core 0.16.3 Released Bitcoin Core 0.16.3 is now available with a fix for a denial-of-service vulnerability affecting earlier versions of Bitcoin Core. $ ./bitcoind -daemon bitcoin server starting $ ./bitcoin-cli -rpcwait help # shows the help text A list of RPC calls will be shown. $ ./bitcoin-cli getbalance 2000.00000 If you are learning the API, it is a very good idea to use the test network (run bitcoind -testnet and bitcoin-cli -testnet). JSON-RPC Documentation #8754 0e2c6bd Target protobuf 2.6 in OS X build notes. (fanquake) #8461 b17a3f9 Document return value of networkhashps for getmininginfo RPC endpoint (jlopp) #8512 156e305 Corrected JSON typo on setban of net.cpp (sevastos) #8683 8a7d7ff Fix incorrect file name bitcoin.qrc (bitcoinsSG) #8891 5e0dd9e Update bips.md for Segregated Bitcoin Core should also work on most other Unix-like systems but is not as frequently tested on them. From 0.17.0 onwards, macOS <10.10 is no longer supported. 0.17.0 is built using Qt 5.9.x, which doesn’t support versions of macOS older than 10.10. Additionally, Bitcoin Core does not yet change appearance when macOS “dark mode” is Bitcoin.org is a community funded project, donations are appreciated and used to improve the website. Make a donation #18499 Make rpc documentation not depend on call-time rpc args (MarcoFalke) #18532 Avoid initialization-order-fiasco on static CRPCCommand tables (MarcoFalke)

[index] [16644] [10084] [25386] [29514] [19240] [3742] [13498] [28184] [4801] [8010]

Bitcoin JSON-RPC Tutorial 4 - Command Line Interface

Bitcoin JSON-RPC Tutorial 4 - Command Line Interface - Duration: 5:14. m1xolyd1an 11,014 views. 5:14. Building a 3.5kWh DIY Solar Generator for $650 - Start to Finish - Duration: 33:01. Bitcoin JSON-RPC tutorial. Making your first bitcoin JSON-RPC calls in PHP. My Book: https://www.amazon.com/Building-Bitco... BTC: 1NPrfWgJfkANmd1jt88A141PjhiarT8d9U. Bitcoin JSON-RPC tutorial. Handling JSON, entering parameters and receiving error messages. BTC: 1NPrfWgJfkANmd1jt88A141PjhiarT8d9U. 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... An introduction to the Bitcoin JSON-RPC tutorial series. BTC: 1NPrfWgJfkANmd1jt88A141PjhiarT8d9U.

Flag Counter