|
Subject |
Started by  |
Replies |
Views |
Last post |
|
|
Trouble importing keys
|
Bungeebones
|
3
|
1266
|
June 18, 2014, 07:16:43 PM
by fbueller
|
|
|
A Hierarchical Data Storage System For Hierchical Addresses and Keys
|
Bungeebones
|
0
|
2347
|
June 27, 2014, 01:59:21 PM
by Bungeebones
|
|
|
A basic question about addresses
|
Bungeebones
|
3
|
833
|
August 05, 2014, 03:35:41 PM
by Bungeebones
|
|
|
Is a reduced reward time possible?
« 1 2 All »
|
Bungeebones
|
25
|
2913
|
January 25, 2016, 02:17:12 PM
by mamadmankan
|
|
|
PHP Only Partially Reading Bitcoind
|
Bungeebones
|
7
|
659
|
April 09, 2014, 11:58:23 PM
by Bungeebones
|
|
|
How was name coin created?
|
Bungeebones
|
10
|
808
|
June 26, 2013, 02:33:41 PM
by PerfectAgent
|
|
|
Deterministic addresses and testnet
|
Bungeebones
|
1
|
475
|
June 15, 2014, 02:04:01 PM
by Bungeebones
|
|
|
Is a programmable client possible?
|
Bungeebones
|
4
|
523
|
April 23, 2014, 12:49:51 AM
by Bungeebones
|
|
|
Script review before presenting to PHP developer meetup
|
Bungeebones
|
1
|
1328
|
November 10, 2014, 01:17:01 AM
by LuaPod
|
|
|
A simple question about command line
|
Bungeebones
|
1
|
428
|
April 24, 2014, 12:50:55 AM
by mcaizgk2
|
|
|
why bitcoin mining difficulty is increased?
« 1 2 3 4 5 All »
|
Burks
|
87
|
4622
|
March 02, 2018, 06:48:27 PM
by defrix
|
|
|
Bad signatures leading to 55.82152538 BTC theft (so far)
« 1 2 ... 6 7 All »
|
BurtW
|
136
|
58209
|
August 31, 2017, 05:15:05 AM
by gmaxwell
|
|
|
The case for moving from a 160 bit to a 256 bit Bitcoin address
« 1 2 3 All »
|
BurtW
|
57
|
6453
|
June 28, 2017, 04:22:47 PM
by TierNolan
|
|
|
Two Bitcoins addresses for the same public key?
|
BurtW
|
9
|
7505
|
June 01, 2013, 11:38:59 AM
by jackjack
|
|
|
1BitcoinEaterAddressDontSend
« 1 2 All »
|
BurtW
|
24
|
3953
|
September 09, 2013, 11:05:48 PM
by BurtW
|
|
|
Need some clarification on usage of the nonce in version message
|
BusinessChain
|
7
|
122
|
July 26, 2018, 03:11:43 PM
by gmaxwell
|
|
|
Why does 256-bit ECC offers equivalent security of 128-bit symmetric encryption?
|
BusyBeaverHP
|
2
|
728
|
March 31, 2015, 02:08:31 AM
by DeathAndTaxes
|
|
|
OP_EVAL proposal
« 1 2 3 4 All »
|
ByteCoin
|
70
|
12604
|
May 24, 2013, 02:50:07 PM
by jgarzik
|
|
|
Untraceable transactions which can contain a secure message are inevitable.
|
ByteCoin
|
11
|
15627
|
October 19, 2014, 05:58:27 PM
by dNote
|
|
|
Can you attach a fee payment to a transaction you haven't signed?
|
ByteCoin
|
2
|
644
|
April 01, 2012, 12:18:33 AM
by da2ce7
|
|
|
Managing substantial changes to Bitcoin - a QA network.
|
ByteCoin
|
19
|
3995
|
May 20, 2011, 05:49:20 PM
by anisoptera
|
|
|
OP_NOP-appended transactions - how long do non-standard transactions wait?
|
ByteCoin
|
10
|
1697
|
June 06, 2011, 12:13:42 PM
by ene
|
|
|
Some nLockTime and transaction hash calculation questions
|
ByteCoin
|
5
|
1037
|
September 21, 2011, 04:34:25 PM
by etotheipi
|
|
|
OP_CHECKMULTISIG - how does it work?
|
ByteCoin
|
5
|
2760
|
August 23, 2011, 09:02:02 PM
by Gavin Andresen
|
|
|
(a and b) OR c transactions
|
ByteCoin
|
1
|
916
|
December 13, 2011, 09:26:23 AM
by finway
|
|
|
"wallet" handling code should be a separate process.
|
ByteCoin
|
14
|
1987
|
November 18, 2010, 08:33:46 AM
by wumpus
|
|
|
New Paper: Deanonymisation of clients in Bitcoin P2P network
« 1 2 All »
|
ByteCoin
|
38
|
7825
|
June 24, 2014, 06:22:00 PM
by Gavin Andresen
|
|
|
Justification for keeping IsStandard and introducing new standard tx types
|
ByteCoin
|
1
|
5022
|
August 23, 2011, 10:51:42 PM
by Gavin Andresen
|
|
|
No "wallet protection services" without (A and B) or C transactions
|
ByteCoin
|
16
|
2700
|
December 26, 2011, 04:47:38 AM
by casascius
|
|
|
Orphan blocks - how to reduce
|
ByteCoin
|
1
|
2145
|
November 25, 2010, 07:17:28 AM
by lfm
|
|
|
VOTE: The name for Bitcoin Improvement Proposals
|
ByteCoin
|
4
|
653
|
September 20, 2011, 08:43:08 PM
by Alex Zee
|
|
|
Protecting privacy without generating and distributing new addresses.
|
ByteCoin
|
10
|
1489
|
August 31, 2011, 11:51:34 PM
by etotheipi
|
|
|
DoS countermeasures may facilitate network fragmentation attacks
|
ByteCoin
|
3
|
1259
|
September 21, 2011, 12:44:29 PM
by Gavin Andresen
|
|
|
Constructing transactions without access to the block-chain
|
ByteCoin
|
5
|
956
|
October 05, 2011, 03:35:37 PM
by Mike Hearn
|
|
|
Need OP_BLOCKNUMBER to allow "time" limited transactions
|
ByteCoin
|
11
|
4542
|
November 18, 2010, 09:10:36 PM
by RHorning
|
|
|
Most transaction relaying is currently pointless and wastefull
|
ByteCoin
|
13
|
1338
|
August 12, 2011, 01:43:48 PM
by Gavin Andresen
|
|
|
Trasactions with "sequence":0
|
ByteCoin
|
1
|
735
|
June 06, 2011, 06:50:24 PM
by Mike Hearn
|
|
|
ECDSA signature verification requires an unnecessary modular inversion
|
ByteCoin
|
0
|
1376
|
April 20, 2011, 01:14:56 PM
by ByteCoin
|
|
|
Discouraging "Selfish" mining
|
ByteCoin
|
19
|
4625
|
December 31, 2013, 11:24:20 PM
by King Lear
|
|
|
Hiding the recipient and amount until the money is spent
|
ByteCoin
|
10
|
8220
|
August 17, 2010, 06:27:42 AM
by lfm
|