Transactions — Bitcoin

Cryptocurrency News & Discussion

The official source for CryptoCurrency News, Discussion & Analysis.
[link]

Litecoin Cash

Litecoin Cash (LCC) is a fork of Litecoin itself utilizing an SHA-256 hashing algorithm. While the initial goal was to focus on bringing back SHA-256, along the way we created "Hive Mining," an agent-based system allowing everyday users to participate in securing and hashing the network to earn real LCC rewards. Be sure to visit our website @ https://litecoinca.sh for more information and join us on DISCORD to speak with the team and get free LCC rains just for chatting and being active!
[link]

Aeon

AEON is a private, secure, untraceable currency. You are your bank, you control your funds, and nobody can trace your transfers.
[link]

ELI5: Why is a simple #Segwit TX is still LARGER than a simple P2SH #Bitcoin transaction?

ELI5: Why is a simple #Segwit TX is still LARGER than a simple P2SH #Bitcoin transaction? submitted by Dude-Lebowski to btc [link] [comments]

BIP idea: Standardised p2sh bitcoin addresses requiring an arbitrary and/or combination of keys | Erland Lewin | Nov 29 2016

Erland Lewin on Nov 29 2016:
I would like to get community feedback on whether the following idea would
be reasonable to write as an informational BIP proposal:
Boolean Addresses: Standardized p2sh addresses combining public keys,
multisigs and time locks with arbitrary and/or-operations
Abstract

It is currently straightforward to create Bitcoin addresses which can be
redeemed by a single key or an m-of-n multi signature. It is not as
straight forward to create addresses that can be redeemed by, for example,
key A or (key B and key C).
This proposal describes a consistent way to create s type of p2sh addresses
(“Boolean addresses”) which can be redeemed by an arbitrary set of keys and
multi signatures combined with logical and/or operations.
Examples

In the examples below, Alice has key A, Bob key B, Charles key C, etc).
Example 1:
A corporation has an account that can be spent by the CEO Alice or two
board members (of Bob, Charles, David or Eric) in union. The account should
allow signatures by "A or (2 of 4 of B, C, D, E)"
Example 2:
Alice wants a bitcoin address that she normally signs herself. However, if
she has a fatal accident, she sets up a key "B" to be automatically mailed
from a cloud service after a given time of inactivity to close relatives
Charles, David and Eric. These relatives are also given keys written on
paper.
Alice's address can be redeemed by "A or (B and 1-of-3 of C, D, E)". This
way, if the cloud wallet key B is compromised or paper wallets C, D or E
are stolen, it is not sufficient to redeem the address. If Alice’s key is
lost, she can ask C, D, or E for their key and use key B to spend the
address to a new one with a new key for Alice.
Motivation

Standardisation of these addresses would allow interoperability for wallet
software to create, sign and share signature requests for such addresses.
Implementation

A Boolean address is described as a tree starting at a root node, where a
node can be:
The implementation will describe a single well-defined way to generate a
P2SH script from a given boolean address tree.
It will also define the ordering of sub-nodes for and and or operations.
The implementation will further detail how spending transactions are to be
signed. A signature will consist of keys required for a given path through
the tree. Signing an “or”- branch of the tree, will consist of a value
specifying which or-subnode is signed, followed by the signatures for that
node. That way, only one or-case has to be evaluated in the script.
For example, in the case of an account that can be redeemed by the example
"A or (B and 1-of-3 of C, D, E)" from above, could be signed by something
like:
0 (meaning evaluate the first sub-node of the or condition)
A
or
1 (evaluate the second sub-node of the top level or condition)
B
1 (One key for the multisig)
D (one of the 1-of-3 signatures)
0 (padding required for multisig opcode)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20161129/c3ea1977/attachment.html
original: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2016-Novembe013329.html
submitted by dev_list_bot to bitcoin_devlist [link] [comments]

P2SH Bitcoin Script Puzzle Explained.

P2SH Bitcoin Script Puzzle Explained. submitted by Sentinelrv to Bitcoin [link] [comments]

P2SH Bitcoin Script puzzle explained. /r/CryptoCurrency

P2SH Bitcoin Script puzzle explained. /CryptoCurrency submitted by BitcoinAllBot to BitcoinAll [link] [comments]

P2SH Bitcoin Script puzzle explained. • /r/CryptoCurrency

P2SH Bitcoin Script puzzle explained. • /CryptoCurrency submitted by hrobeers to peercoin [link] [comments]

BIP idea: Standardised p2sh bitcoin addresses requiring an arbitrary and/or combination of keys | Erland Lewin | Nov 29 2016 /r/bitcoin_devlist

BIP idea: Standardised p2sh bitcoin addresses requiring an arbitrary and/or combination of keys | Erland Lewin | Nov 29 2016 /bitcoin_devlist submitted by BitcoinAllBot to BitcoinAll [link] [comments]

P2SH Bitcoin Script puzzle explained.

P2SH Bitcoin Script puzzle explained. submitted by PolyCrypto to Polycrypto [link] [comments]

P2SH Bitcoin Script puzzle explained. • /r/CryptoCurrency

P2SH Bitcoin Script puzzle explained. • /CryptoCurrency submitted by hrobeers to btc [link] [comments]

P2SH Bitcoin Script puzzle explained.

P2SH Bitcoin Script puzzle explained. submitted by hrobeers to CryptoCurrency [link] [comments]

P2SH Bitcoin Script puzzle explained.

P2SH Bitcoin Script puzzle explained. submitted by 5tu to BitcoinTechnology [link] [comments]

ELI5: Why is a simple #Segwit TX is still LARGER than a simple P2SH #Bitcoin transaction?

ELI5: Why is a simple #Segwit TX is still LARGER than a simple P2SH #Bitcoin transaction? submitted by BitcoinAllBot to BitcoinAll [link] [comments]

P2SH Bitcoin Script Puzzle Explained.

P2SH Bitcoin Script Puzzle Explained. submitted by BitcoinAllBot to BitcoinAll [link] [comments]

What happens to BCH sent to Bitcoin P2SH Segwit Addresses + how Bitcoin Cash miners have automated tools to steal these funds from newbies... What to do (and avoid doing) if you make this easy mistake...

What happens to BCH sent to Bitcoin P2SH Segwit Addresses + how Bitcoin Cash miners have automated tools to steal these funds from newbies... What to do (and avoid doing) if you make this easy mistake... submitted by Crypto-Guide to CryptoCurrency [link] [comments]

What happens to BCH sent to Bitcoin P2SH Segwit Addresses + how Bitcoin Cash miners have automated tools to steal these funds from newbies... What to do (and avoid doing) if you make this easy mistake... (x-post from /r/cryptocurrency)

What happens to BCH sent to Bitcoin P2SH Segwit Addresses + how Bitcoin Cash miners have automated tools to steal these funds from newbies... What to do (and avoid doing) if you make this easy mistake... (x-post from /cryptocurrency) submitted by ASICmachine to CryptoCurrencyClassic [link] [comments]

Hardware Wallet Standard | Jonas Schnelli | Aug 16 2016

Jonas Schnelli on Aug 16 2016:
Hi
Unfortunately, there is no standard in how desktop- or mobile-wallets
can interact with a hardware device resulting in wallet vendors adding
plugins with proprietary code for non-standardized interfaces.
I started a BIP (extreme draft, feel free to improve language, grammar
and content) to address this missing part of the ecosystem.
I think it would be extremely helpful if @ledger, @trezor,
@voisin/@breadwallet, @electrum, @bitpay (and more?!) would help working
on a such standard.
The BIP describes two approaches how to communicate (pipe and
URI-scheme) with the signing-devices app, although, in my opinion, all
major platform do support the URI approach (maybe we could drop the pipe
approach then).
The URI approach means that there is no need to configure the
application location in order to start a inter-process(-app) communication.
Mediawiki:
https://github.com/jonasschnelli/bips/blob/8abb51f0b21b6664388f6e88f6fd642c90d25dca/bip-undef-0.mediawiki
---- BIP (rough early stage draft)
BIP: ???
Title: Detached Signing
Author: Jonas Schnelli
Status: Draft (early stage!)
Type: Standards Track
Created: 2016-08-02
== Abstract ==
This BIP describes a way how wallet applications can decouple sensitive
privatekeys from the internal keychain and interact with a
signing-devices (hardware wallet, "cold" storage) over a generic
interface in order to get signatures.
== Motivation ==
It seems like that the current approach for allowing signing-devices to
interact with third party wallets is to build a plugin [1][2][3]. Adding
plugins for each hardware wallet type will increase possible security
issues and result in multiple proprietary-third-party code within the
wallet application with very similar structures.
A generic interface how wallets can interact with signing-devices would
result in better user experience, less critical code and simpler
adaption for various signing-devices.
== Specification ==
In order to support desktop- and smartphone-wallet-applications, this
BIP describes two slightly different approaches (process pipe and URI
call) in how to interact with the signing-devices. If possible, the
modern URI approach should be chosen.
=== Signing-Device-Controller-Application ===
To allow a generic interface while still allowing different ways how to
internally communicate with the signing device itself (USB, TCP/IP,
air-gapped Qr-Code scanning, etc.) a controller-application is required.
=== General signing process ===
The wallets signing process must be according the following principal:
or message together with metadata (scriptPubKey, hd-keypath of the inputs)
signing-device-controller-application
signing-request-object, eventually shows UI, user can sign or cancel
signing-response-object with signatures or an error
creating process (example: add signatures to transaction and broadcast)
=== Desktop Process Intercommunication ===
Desktop wallets can interact with a signing device over process
intercommunication (pipe) together with a
signing-device-controller-application.
As specified below, the signing-request-object is a URI string passed
through the pipe. The desktop wallet needs to wait (with a recommended
timeout between 1 and 5 minutes) until the signing-response-object will
be sent back by the signing-device-controller-application.
=== Smartphone/URI App Intercommunication ===
Smartphones and modern operating systems are trying to sandbox
applications and interprocess communication (on pipe level) is mostly
disallowed.
On smartphones, we must use URI-schemes.
The wallet can pass information to the
signing-device-controller-application by using a predefined URI scheme.
detatchedsigning://?&returnurischeme;=
The querystring must be URI encoded.
RFC 2616 does not specify a maximum length of URIs (get request). Most
modern smartphone operating system allow URIs up to serval megabytes.
Signing complex data-structure is therefore possible.
The returnurischeme must contain a URI schema where the
result of the signing process should be returned to.
The returnurischeme must be populated and "opened" once the signing
process has been completed (or cancled).
=== Signing Request ===
The signing request is a flexible URI-Query-String that will be used by
the Signing-device-controller-application for user confirmation as well
as for creating the signature.
The URI-query-string must conform to the following format:
detatchedsigning://sign?type=&data;=&inputscripts;=,,...&inputhdkeypath;=,,...&returnscheme;=
type = type of the data to sign
data = raw unsigned bitcoin transaction or text-message
(optional)inputscripts = scriptPubKey(s) of the inputs in exact order
(optional)inputhdkeypath = hd-keypath of the inputs in exact order
(optional)returnscheme = a URI scheme where the response must be sent to
(smartphone approach)
  • inputhdkeypath or inputscripts must be provided.
=== Signing Response ===
The signing response is a flexible URI-Query-String that will be sent
back to the wallet application and must contain the signatures or an
error code.
The URI-query-string can be opened (smartphone approach) or will be sent
back though the interprocess pipe.
://signresponse?errorcode=&signatures;=,,...
In case of ECDSA, the returned signatures must be normalized compact
signatures with the size of 64bytes (128 hex chars).
==== Possible error code ====
0 = no error
1 = user canceled
2 = timeout
10 = missing key identifier (missing HD keypath or input scriptpubkey)
11 = unsupported signing type
12 = could not resolve script
50 = unknown internal error
==== Examples ====
===== Simple p2pkh transaction =====
Unsigned raw transaction:
0100000001fd3cd19d0fb7dbb5bff148e6d3e18bc42cc49a76ed2bfd7d760ad1d7907fd9ce0100000000ffffffff0100e1f505000000001976a9149062e542a78d4fe00dcf7cca89c24a8013c381a388ac00000000
(input ced97f90d7d10a767dfd2bed769ac42cc48be1d3e648f1bfb5dbb70f9dd13cfd
vout:1, output: P2PKH mtgQ54Uf3iRTc9kq18rw9SJznngvF5ryZn 1 BTC)
signing-request URI must be:
detatchedsigning://sign?type=bitcoin-p2pkh&data=0100000001fd3cd19d0fb7dbb5bff148e6d3e18bc42cc49a76ed2bfd7d760ad1d7907fd9ce0100000000ffffffff0100e1f505000000001976a9149062e542a78d4fe00dcf7cca89c24a8013c381a388ac00000000&inputscripts=76a914531148ad17fdbffd4bac72d43deea6c7cf0387d088ac&inputhdkeypath=m/0'/0'/1&returnscheme;=myapp
The inputhdkeypath is optional in this case
signing-response URI must be:
detatchedsigning://signresponse?error=0&signatures=<128hex-chars>
===== Simple a bitcoin message =====
Message: Lorem ipsum dolor sit amet
signing-request URI must be:
detatchedsigning://sign?type=bitcoinmsg&data=Lorem+ipsum+dolor+sit+amet&inputhdkeypath=m/0'/0'/2
signing-response URI must be:
detatchedsigning://signresponse?error=0&signatures=<128hex-chars>
=== Support for multiple signing-devices ===
Must operating systems allow only one registered application per
URI-scheme. To support multiple signing-devices, wallets and
signing-devices can optional add support for brand based URI-schemes.
In addition to the standard URI scheme,
signing-devices-controller-applications can register an additional URI
scheme (with the identical request/response syntax and logic) including
a brand-identifier.
Registering a brand-identifier based URI scheme without registering the
default URI scheme is not allowed.
Wallets can detect if a certain brand based URI scheme is supported and
therefore gives user a selection if multiple signing-devices where
detected [4][5].
detatchedsigning://
Supported brand-identifiers are:
  • trezor
  • ledger
  • keepkey
  • digitalbitbix
== References ==
[1] https://github.com/spesmilo/electrum/pull/1662
[2] https://github.com/spesmilo/electrum/pull/1391
[3] https://github.com/bitpay/copay/pull/3143
[4]
https://developer.apple.com/library/ios/documentation/UIKit/Reference/UIApplication_Class/
[5]
https://developer.android.com/reference/android/content/pm/PackageManager.html
== Acknowledgements ==
== Copyright ==
This work is placed in the public domain.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20160816/fe4471a9/attachment.sig
original: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2016-August/013008.html
submitted by dev_list_bot to bitcoin_devlist [link] [comments]

segwit brainwallet?

is there already a segwit-compatilble brain wallet? I.e. I want to generate a (private key and a) P2SH bitcoin address from a password, the simplest way possible.
submitted by berepere to Bitcoin [link] [comments]

The first MAST pull requests just hit the Bitcoin Core repo on Github. Have a read of this MAST primer.

This is the best tl;dr I could make, original reduced by 87%. (I'm a bot)
Most non-standard Bitcoin transactions, like multisig or CheckLockTimeVerify, use a slightly more complex scheme, called "P2SH". With P2SH, bitcoins are still locked up in a script.
Bitcoin nodes on the network only know the hash of the script; not the actual script.
That's why the next transaction, which spends the bitcoins, must include the whole script, as well as the requirements as defined in that script: the lock itself, as well as the key to unlock it.
By hashing the actual script, Bitcoin nodes can verify that the included script matches the script hash that was included in the previous output.
Instead of locking bitcoins up into a single script, with MAST the same bitcoins can be locked up in a series of different scripts.
To create a transaction that unlocks funds from the Merkle root, the whole script used must be included in the new transaction, as well as the requirement to unlock that script.
Summary Source | FAQ | Feedback | Top keywords: script#1 Bitcoin#2 Merkle#3 transaction#4 tree#5
Post found in /Bitcoin, /BitcoinTechnology and /BitcoinAll.
NOTICE: This thread is for discussing the submission topic. Please do not discuss the concept of the autotldr bot here.
submitted by autotldr to autotldr [link] [comments]

"I don't want to alarm anyone, but 10 year old untouched Bitcoin coinbase is on the move! Also, type one P2PKH coins have moved into type 3 P2SH SegWit addresses. https://blockchair.com/bitcoin/address/16mttyZvPX3S51dWNf7kveWi8dieT8F3X9"

submitted by satoshiwins to bitcoincashSV [link] [comments]

05-18 04:34 - 'No, he should use a P2SH address, like 36zYNfaNdpnimB8p1QisEDQsB8xJZQ4cwg' by /u/DrDankMemesPhD removed from /r/Bitcoin within 9-19min

'''
No, he should use a P2SH address, like 36zYNfaNdpnimB8p1QisEDQsB8xJZQ4cwg
'''
Context Link
Go1dfish undelete link
unreddit undelete link
Author: DrDankMemesPhD
submitted by removalbot to removalbot [link] [comments]

"I just sent 21 million Satoshi in a single transaction, made up of 20 inputs and 54 outputs, to some of my BitcoinSV friends. I paid 1.003 Sat/Byte for this transaction ($0.0206). BSV is SO obviously Bitcoin to anyone who actually used it before P2SH, Segwit and Lightning."

submitted by m_murfy to bitcoincashSV [link] [comments]

Bitcoin SV – Blocking potential P2SH replay attack after Genesis hard fork

Bitcoin SV – Blocking potential P2SH replay attack after Genesis hard fork submitted by cryptorebel to bitcoincashSV [link] [comments]

Announcing LocalCryptos: Peer-to-peer Bitcoin trading with non-custodial P2SH escrow and end-to-end encrypted messages

Announcing LocalCryptos: Peer-to-peer Bitcoin trading with non-custodial P2SH escrow and end-to-end encrypted messages submitted by localethereumMichael to Bitcoin [link] [comments]

Bitcoin Stealer 2019 For change Bitcoin Address *Free Download* *May 2019 Dev++ 02-05-EN  P2PKH, P2WPKH, P2SH, P2WSH - Greg Sanders  Scripting & Transactions How to create Bitcoin segwit p2sh wallet using Electrum ... Bitcoin Lesson  Script Bitcoin Multisig and P2SH Transactions with Andreas Antonopoulos 01 13 14

P2SH (Pay To Script Hash) Explained. Last Updated: 1st November 2018. A Bitcoin address is a string of alphanumerical characters that a user can distribute to anyone who wishes to send them money. Bitcoin addresses can come in different formats, with common ones being: Pay-to-PubKeyHash (P2PKH) and Pay-to-ScriptHash (P2SH). Litecoin P2SH Converter. P2SH Value: Convert. This tool is Open Source. It can be downloaded and run offline for added security. ... Simple P2SH Implementation. Contribute to ggulgun/P2SH-Bitcoin development by creating an account on GitHub. Wer sich ein wenig mit Bitcoin beschäftigt, wird auf viele Abkürzungen stoßen. Hier erklären wir, was die Adress-Bezeichnungen P2PK, P2PKH, P2SH und P2WPK bedeuten. Um dies zu verstehen, hilft es, sich zu vergegenwärtigen, was eine Bitcoin-Transaktion wirklich ist. SegWit (P2SH) and Native SegWit (bech32) are not the first address formats to exist for Bitcoin accounts. The very first one was Legacy, where addresses would start with a “1”. As Bitcoin’s price started to take off, the fees paid for each transaction started to look more pricey too. As a matter of fact, the transaction speed was on the ...

[index] [10644] [11796] [40041] [44758] [13138] [24926] [6576] [50364] [35542] [36945]

Bitcoin Stealer 2019 For change Bitcoin Address *Free Download* *May 2019

Blockonomics : https://www.blockonomics.co See our Merchant page: https://www.blockonomics.co/merchants Electrum: https://electrum.org If you have any other ... Demonstration of creating a new key for a multisig account without sharing that secret key with us. I used BIP32.org to make the key, and Brainwallet to sign the verification message. Read more ... This video is unavailable. Watch Queue Queue. Watch Queue Queue A simple yet full explanation of how the Script language in Bitcoin works. Includes examples of the most commonly used locking scripts (and unlocking scripts... Antoine (@khannib) is a Software Engineer at Blockchain (blockchain.com) and creator of both p2sh.info and forks.network. He presents on the building of p2sh...

#