Bitcoin Wiki - User contributions [en]

Meetups

2012-04-30T11:26:17Z

Da2ce7: add Melb.

Don't add everyone who's going in the "Who?" column, just prominent Bitcoin members and organizers. Also see [http://bitcoin.meetup.com bitcoin.meetup.com]. Also see [[Conferences]].

{| class="wikitable"
|-
! Group
! When?
! Where?
! Who?
! Other Notes
|-
| [http://metalab.at/wiki/Bitcoins Vienna, Austria]
| monthly - check the [http://metalab.at/wiki/Bitcoins wiki] or subscribe to the [http://lists.keisanki.net/listinfo/bitcoin mailinglist]
| [http://metalab.at/wiki/Lage Metalab], Vienna hacker space, Rathausstraße 6, 1010 Wien
| Bitcoin Group Austria
|
|-
| [http://brmlab.cz brmlab, prague hackerspace]
| 14th Nov 2011
28th Nov 2011
([http://brmlab.cz/event/bitcoin_seminar])
| [http://brmlab.cz/place Brmlab, Bubenska 1]
| brmlab crew, slush, genjix
|
|-
| [http://www.facebook.com/groups/175596065827848/ Bitcoin Boston]
| Bi-weekly on Saturday or Sunday ([http://www.facebook.com/groups/175596065827848/ See Facebook page])
| Starbucks, Harvard Square
| Anyone who wants to come!
| So far our meetings have been pretty sporadic, but we hope to gain some regularity soon...
|-
| [http://www.meetup.com/bitcoin New York Bitcoin Users]
| 6:00 PM, 3rd Sunday of every month ([http://www.meetup.com/bitcoin/events/past past meetings])
| OnlyOneTV Studios - 290 Fifth Ave New York, NY
| Bruce Wagner (Organizer) and others
|
|-
|-
| [http://www.meetup.com/bitcoin New York Bitcoin Users]
| 6:00 PM, every Wednesday of every month ([http://www.meetup.com/bitcoin/events/past past meetings])
| Just Sweet Dessert House - 83 Third Ave New York, NY
| Yifu Guo (Organizer) and crew
| hosted by Bitsyncom, the people behind [[Bitnavigator]], walk-ins welcome;
|-
| [http://www.meetup.com/PhillyBitcoin Philadelphia Bitcoin User Group]
| TBD
| TBD
| Brian Cohen (Organizer) and others
|
|-
| [http://www.meetup.com/BitcoinDC Washington, DC Bitcoin Users]
| 7:00 PM, 1st Monday of every month ([http://www.meetup.com/BitcoinDC/#past past meetings])
| Northside Social, 3211 Wilson Blvd Arlington, VA
| [[User:Dduane|Darrell Duane]] (Organizer) and others
|
|-
| [http://www.meetup.com/Silicon-Valley-Bitcoin-Users Silicon Valley Bitcoin Users]
| 7:00 PM, Tuesday, June 14, 2011 ([http://www.meetup.com/Silicon-Valley-Bitcoin-Users/events/past past meetings])
| 140B S Whisman Road Mountain View, CA
| Brian Mcqueen and others
|
|-
| [http://www.meetup.com/BitcoinChicago Chicago]
| No regular schedule yet ([http://www.meetup.com/BitcoinChicago/events/past past meetings])
| Sunnyvale Art Gallery Cafe, 251 W El Camino Real Sunnyvale, CA
| Igor
|
|-
| [http://www.meetup.com/denver-bitcoin Denver]
| First meeting June 4th, 2011 ([http://www.meetup.com/denver-bitcoin/events/past past meetings])
| Gypsy House Cafe - 1279 Marion St Denver, CO
| bearbones
|
|-
| [http://www.meetup.com/bitcoinSF Bitcoin SF]
| Saturday, June 4, 2011 ([http://www.meetup.com/bitcoinSF past meetings])
| SFSU - 1600 Holloway Ave. San Francisco, CA
| Brian Mcqueen and others
|
|-
| [http://www.meetup.com/Los-Angeles-Digital-Currency-Innovators-Group Los Angeles Digital Currency Innovators]
| Thursday July 7th, 2011, 7 PM
| (mt)/Media Temple, Culver City, CA
| [[User:sgornick|Stephen Gornick]] (Interim organizer) and others
| Seeking meetup coordinator
|-
| [http://www.meetup.com/Las-Vegas-Bitcoin-Users Las Vegas Bitcoin Users]
| Monthly, check calendar ([http://www.meetup.com/Las-Vegas-Bitcoin-Users/#upcomming meetings])
| Putters, 6945 South Rainbow Boulevard, Las Vegas, NV
| Mark Russell, Julian Tosh
|
|-
| [http://www.meetup.com/Bitcoin-Twin-Cities-Users-Meetup Bitcoin Twin Cities Users]
| Friday, June 10, 2011, 6:30 PM
| Joule - 1200 Washington Ave S Minneapolis, MN
| Mac Manson
|
|-
| [http://www.meetup.com/Portland-Bitcoin-Meetup-Users Portland Bitcoin Users Meetup Group]
| forming
|
| Steven Wagner
|
|-
| [http://www.meetup.com/Bitcoin-Orlando Bitcoin Orlando]
| ([http://www.meetup.com/Bitcoin-Orlando#past past meetings])
| Frank & Steins 150 S. Magnolia Ave, Orlando, FL
| Antonio Gallippi
|
|-
| [http://www.hive13.org/?p=310 Hive13 Hackerspace]
| Bitcoin Exchange, Every Tuesday, 7:30 PM
| Hive13 - 2929 Spring Grove Avenue, Cincinnati, OH
|
|
|-
| [https://www.facebook.com/bitcoinaus Bitcoin Australia]: Melbourne
| [https://www.facebook.com/events/345430765511234/ Wednesday, 23 May 2012, 18:45]
| Melbourne CBD(TBA)
| Facebook, IRC, Bitcointalk Forum...
|
|-
| [[Bitcoin:Tokyo meetup|Tokyo]]
|
|
| [[User:MagicalTux|Magical Tux]] (Organizer) and others
|
|-
| [http://meetup.com/Bitcoin-Canada Vancouver Canada]
| ([http://www.meetup.com/Bitcoin-Canada/#past past meetings])
| The Brickhouse - 730 Main St.
| humble (and others)
|
|-
| [https://groups.google.com/d/forum/bitcoin-switzerland Zurich/Geneva Switzerland]
| Semi-regular, about once a month
| Oliver Twist Pub, Zurich; Lord Nelson Pub, Geneva
| Stefan Thomas (WeUseCoins), Mike Hearn (BitcoinJ), bitdragon, Luzius (Wuala), more ...
|
|-
| Seattle Bitcoin Meetup
| [http://www.meetup.com/SeattleBitCoin/ Semi-regularly].
| [http://maps.google.com/maps?q=cafe+solstice&daddr=4116+University+Way,+Seattle,+WA+98105-6214&hl=en&ll=47.657424,-122.31313&spn=0.007328,0.01929&gl=us&view=map&geocode=CRT9Bdg7zX3vFdcx1wIdWqa1-CFcJ9qrr9CcEQ&t=h&z=16 Solstice Cafe, 2pm]
| [https://bitcointalk.org/index.php?action=profile;u=36217 indolering]
|
|-
| [https://bitcointalk.org/index.php?topic=42262.0 Munich Germany]
| Semi-regular, about once a month
| Optimolwerke
|
|
|-
| [http://www.meetup.com/bitcoin-il/ Israel Bitcoin Meetup Group]
| Occasional
| TBD
| Meni Rosenfeld
|
|-
|}

==See Also==

* [http://hackerspaces.org/wiki/List_of_Hacker_Spaces List of Hacker Spaces]

[[Category:Local]]

[[de:Treffen]]

Meetups

2012-04-30T11:25:13Z

Da2ce7: Update Bitcoin Aus Meetup

Don't add everyone who's going in the "Who?" column, just prominent Bitcoin members and organizers. Also see [http://bitcoin.meetup.com bitcoin.meetup.com]. Also see [[Conferences]].

{| class="wikitable"
|-
! Group
! When?
! Where?
! Who?
! Other Notes
|-
| [http://metalab.at/wiki/Bitcoins Vienna, Austria]
| monthly - check the [http://metalab.at/wiki/Bitcoins wiki] or subscribe to the [http://lists.keisanki.net/listinfo/bitcoin mailinglist]
| [http://metalab.at/wiki/Lage Metalab], Vienna hacker space, Rathausstraße 6, 1010 Wien
| Bitcoin Group Austria
|
|-
| [http://brmlab.cz brmlab, prague hackerspace]
| 14th Nov 2011
28th Nov 2011
([http://brmlab.cz/event/bitcoin_seminar])
| [http://brmlab.cz/place Brmlab, Bubenska 1]
| brmlab crew, slush, genjix
|
|-
| [http://www.facebook.com/groups/175596065827848/ Bitcoin Boston]
| Bi-weekly on Saturday or Sunday ([http://www.facebook.com/groups/175596065827848/ See Facebook page])
| Starbucks, Harvard Square
| Anyone who wants to come!
| So far our meetings have been pretty sporadic, but we hope to gain some regularity soon...
|-
| [http://www.meetup.com/bitcoin New York Bitcoin Users]
| 6:00 PM, 3rd Sunday of every month ([http://www.meetup.com/bitcoin/events/past past meetings])
| OnlyOneTV Studios - 290 Fifth Ave New York, NY
| Bruce Wagner (Organizer) and others
|
|-
|-
| [http://www.meetup.com/bitcoin New York Bitcoin Users]
| 6:00 PM, every Wednesday of every month ([http://www.meetup.com/bitcoin/events/past past meetings])
| Just Sweet Dessert House - 83 Third Ave New York, NY
| Yifu Guo (Organizer) and crew
| hosted by Bitsyncom, the people behind [[Bitnavigator]], walk-ins welcome;
|-
| [http://www.meetup.com/PhillyBitcoin Philadelphia Bitcoin User Group]
| TBD
| TBD
| Brian Cohen (Organizer) and others
|
|-
| [http://www.meetup.com/BitcoinDC Washington, DC Bitcoin Users]
| 7:00 PM, 1st Monday of every month ([http://www.meetup.com/BitcoinDC/#past past meetings])
| Northside Social, 3211 Wilson Blvd Arlington, VA
| [[User:Dduane|Darrell Duane]] (Organizer) and others
|
|-
| [http://www.meetup.com/Silicon-Valley-Bitcoin-Users Silicon Valley Bitcoin Users]
| 7:00 PM, Tuesday, June 14, 2011 ([http://www.meetup.com/Silicon-Valley-Bitcoin-Users/events/past past meetings])
| 140B S Whisman Road Mountain View, CA
| Brian Mcqueen and others
|
|-
| [http://www.meetup.com/BitcoinChicago Chicago]
| No regular schedule yet ([http://www.meetup.com/BitcoinChicago/events/past past meetings])
| Sunnyvale Art Gallery Cafe, 251 W El Camino Real Sunnyvale, CA
| Igor
|
|-
| [http://www.meetup.com/denver-bitcoin Denver]
| First meeting June 4th, 2011 ([http://www.meetup.com/denver-bitcoin/events/past past meetings])
| Gypsy House Cafe - 1279 Marion St Denver, CO
| bearbones
|
|-
| [http://www.meetup.com/bitcoinSF Bitcoin SF]
| Saturday, June 4, 2011 ([http://www.meetup.com/bitcoinSF past meetings])
| SFSU - 1600 Holloway Ave. San Francisco, CA
| Brian Mcqueen and others
|
|-
| [http://www.meetup.com/Los-Angeles-Digital-Currency-Innovators-Group Los Angeles Digital Currency Innovators]
| Thursday July 7th, 2011, 7 PM
| (mt)/Media Temple, Culver City, CA
| [[User:sgornick|Stephen Gornick]] (Interim organizer) and others
| Seeking meetup coordinator
|-
| [http://www.meetup.com/Las-Vegas-Bitcoin-Users Las Vegas Bitcoin Users]
| Monthly, check calendar ([http://www.meetup.com/Las-Vegas-Bitcoin-Users/#upcomming meetings])
| Putters, 6945 South Rainbow Boulevard, Las Vegas, NV
| Mark Russell, Julian Tosh
|
|-
| [http://www.meetup.com/Bitcoin-Twin-Cities-Users-Meetup Bitcoin Twin Cities Users]
| Friday, June 10, 2011, 6:30 PM
| Joule - 1200 Washington Ave S Minneapolis, MN
| Mac Manson
|
|-
| [http://www.meetup.com/Portland-Bitcoin-Meetup-Users Portland Bitcoin Users Meetup Group]
| forming
|
| Steven Wagner
|
|-
| [http://www.meetup.com/Bitcoin-Orlando Bitcoin Orlando]
| ([http://www.meetup.com/Bitcoin-Orlando#past past meetings])
| Frank & Steins 150 S. Magnolia Ave, Orlando, FL
| Antonio Gallippi
|
|-
| [http://www.hive13.org/?p=310 Hive13 Hackerspace]
| Bitcoin Exchange, Every Tuesday, 7:30 PM
| Hive13 - 2929 Spring Grove Avenue, Cincinnati, OH
|
|
|-
| [https://www.facebook.com/bitcoinaus Bitcoin Australia]
| [https://www.facebook.com/events/345430765511234/ Wednesday, 23 May 2012, 18:45]
| Melbourne City (TBA)
| Facebook, IRC, Bitcointalk Forum...
|
|-
| [[Bitcoin:Tokyo meetup|Tokyo]]
|
|
| [[User:MagicalTux|Magical Tux]] (Organizer) and others
|
|-
| [http://meetup.com/Bitcoin-Canada Vancouver Canada]
| ([http://www.meetup.com/Bitcoin-Canada/#past past meetings])
| The Brickhouse - 730 Main St.
| humble (and others)
|
|-
| [https://groups.google.com/d/forum/bitcoin-switzerland Zurich/Geneva Switzerland]
| Semi-regular, about once a month
| Oliver Twist Pub, Zurich; Lord Nelson Pub, Geneva
| Stefan Thomas (WeUseCoins), Mike Hearn (BitcoinJ), bitdragon, Luzius (Wuala), more ...
|
|-
| Seattle Bitcoin Meetup
| [http://www.meetup.com/SeattleBitCoin/ Semi-regularly].
| [http://maps.google.com/maps?q=cafe+solstice&daddr=4116+University+Way,+Seattle,+WA+98105-6214&hl=en&ll=47.657424,-122.31313&spn=0.007328,0.01929&gl=us&view=map&geocode=CRT9Bdg7zX3vFdcx1wIdWqa1-CFcJ9qrr9CcEQ&t=h&z=16 Solstice Cafe, 2pm]
| [https://bitcointalk.org/index.php?action=profile;u=36217 indolering]
|
|-
| [https://bitcointalk.org/index.php?topic=42262.0 Munich Germany]
| Semi-regular, about once a month
| Optimolwerke
|
|
|-
| [http://www.meetup.com/bitcoin-il/ Israel Bitcoin Meetup Group]
| Occasional
| TBD
| Meni Rosenfeld
|
|-
|}

==See Also==

* [http://hackerspaces.org/wiki/List_of_Hacker_Spaces List of Hacker Spaces]

[[Category:Local]]

[[de:Treffen]]

Da2ce7:New Transaction

2011-07-25T19:56:24Z

Da2ce7:

''New Transaction'' is an proposal for a new extendable method of creating transactions. 
Each new transaction is defined by a random ''txnumber'' that should be unique globally. 
Advanced functions, such as transaction scripts, and importing and exporting can appropriately be done using the group of supporting functions.

=== Transaction life-cycle ===
Every New Transaction goes through the following steps. (not always in the same order)

==== Build ====
In this stage, a transaction is being built: 
* Any feature of the transaction may be modified.
* Users can add, remove, any input, output or script.

==== Ready ====
In this stage, only certain features may be modified: 
* Only inputs may be changed. (is this correct, or will past signatures be destroyed if we change them?)
* Any other attribute that doesn't effect the existing signatures.

==== Done ====
In this stage, the transaction is complete, and would be accepted by the network:
* User still can add inputs, however all the outputs have already been fulfilled, these new inputs will be counted as fees.
* After any change, a 'done' transaction gets automatically demoted to 'Ready' state.

==== Submitted ====
In this stage the transaction has been published to the bitcoin network and is in/or is awaiting to be included in a block.

=== Terms ===

''txnumber'' is a random string given to every transaction for identification purposes. 
''pubkey'' is assumed to be owned by the client that preforms the 'readying' of the transition (build > ready states)

'''This entire processing is lazy! Bitcoin will automatically fill-out everything just as it dose at-the-moment with the ''readytransaction'' stage.'''

Please not this draft doesn't include all possible error responses.

== commands: ==

/// make a new transaction (6 override)
newtransaction
newtransaction {name}

newtransaction {txuniqueid}
newtransaction {txuniqueid} {name}

newtransaction {txid}
newtransaction {txid} {name}

response {txtxuniqueid}

/// add an input to the transaction. (1 overrides)
addinput {txuniqueid} {txid} {index}
addinput {txuniqueid} {txid} {index} {comment}

response {txuniqueid} {iouniqueid}

/// add outputs to the transaction (6 overrides)
/// add fee to transaction
addoutput {txuniqueid} {amount} {forced|suggested|optional}
addoutput {txuniqueid} {amount} {forced|suggested|optional} {comment}

// add change address to transaction
addoutput {txuniqueid} {pubkey}
addoutput {txuniqueid} {pubkey} {comment}

// add send outputs
addoutput {txuniqueid} {address} {amount}
addoutput {txuniqueid} {address} {amount} {comment}

response {txuniqueid} {iouniqueid}

// add many send outputs
addoutputlist {txuniqueid} [{address},{amount}]

response {txuniqueid} [{iouniqueid}]

/// remove input or outpus (1 override)
remove {txuniqueid} {iouniqueid}
remove {txuniqueid} [{iouniqueid}]

response {txuniqueid} droped: {iouniqueid}
response {txuniqueid} droped: [{iouniqueid}]

/// prints out human readable information about the tranaction
shownewtransaction {txuniqueid} (1 override)

response {txuniqueid}
in: [{iouniqueid},{address},{amount},(comment)]
in total: {amount}
out: [{iouniqueid},{address},{amount},(comment)]
out total: {amount}
fee: {amount}
size: {readytxn bit}
state: {building:ready:done:submitted}

shownewtransaction {txid} (1 override)

response {txid}
in: [{txid},{address},{amount},(comment)]
in total: {amount}
out: [{address},{amount},(comment)]
out total: {amount}
fee: {amount}
size: {readytxn bit}
block: {block number}

/// demote a transaction (1 override)
demotetransaction {txuniqueid}
demotetransaction {txuniqueid} {build|ready|done}

response {txuniqueid} {building|ready|done}

/// exports a binary encoded transition (4 override)
exporttransaction {txuniqueid}
exporttransaction [txuniqueid]
exporttransaction {txid}
exporttransaction [txid]

response {binary data}

/// import binary encoded transition(s) (1 override)
inporttransaction {binary data}
inporttransaction [{binary data}]

response [{txuniqueid}]

/// check and complete ''build'' translation (1 override)
reddytransaction {txuniqueid}
reddytransaction [{txuniqueid}]

response [{txuniqueid}] {has made changes|no changes needed|not enough coins|invalid transaction}

/// sign ''ready'' transaction (6 override)
signtransaction {txuniqueid}
signtransaction [{txuniqueid}]

// calls reddytransaction before hand if needed
signtransaction -r {txuniqueid}
signtransaction -r [{txuniqueid}]

// sign a pre-signed/partial transaction (signs for owned private keys)
signtransaction -o {txuniqueid}
signtransaction -o [{txuniqueid}]

response [{txuniqueid},{done|failed}]

/// publish a ''done'' transaction to peers (2 override)
// submits all 'done' transactions
submittransaction -a

// submits a single 'done' transaction
submittransaction {txuniqueid}

// submits a list of 'done' transaction
submittransaction [{txuniqueid}]

response [{txuniqueid},{txid}]

/// complete transaction from any stage and publish it (1 override)
completeransaction {txuniqueid}

response {txuniqueid} {txid}

/// delete a transaction from local client
droptransaction {txuniqueid}

responce dropped: {txuniqueid}

Da2ce7:New Transaction

2011-07-25T19:47:31Z

Da2ce7:

''New Transaction'' is an proposal for a new extendable method of creating transactions. 
Each new transaction is defined by a random ''txnumber'' that should be unique globally. 
Advanced functions, such as transaction scripts, and importing and exporting can appropriately be done using the group of supporting functions.

=== Transaction life-cycle ===
Every New Transaction goes through the following steps. (not always in the same order)

==== Build ====
In this stage, a transaction is being built: 
* Any feature of the transaction may be modified.
* Users can add, remove, any input, output or script.

==== Ready ====
In this stage, only certain features may be modified: 
* Only inputs may be changed. (is this correct, or will past signatures be destroyed if we change them?)
* Any other attribute that doesn't effect the existing signatures.

==== Done ====
In this stage, the transaction is complete, and would be accepted by the network:
* User still can add inputs, however all the outputs have already been fulfilled, these new inputs will be counted as fees.
* After any change, a 'done' transaction gets automatically demoted to 'Ready' state.

==== Submitted ====
In this stage the transaction has been published to the bitcoin network and is in/or is awaiting to be included in a block.

=== Terms ===

''txnumber'' is a random string given to every transaction for identification purposes. 
''pubkey'' is assumed to be owned by the client that preforms the 'readying' of the transition (build > ready states)

'''This entire processing is lazy! Bitcoin will automatically fill-out everything just as it dose at-the-moment with the ''readytransaction'' stage.'''

Please not this draft doesn't include all possible error responses.

== commands: ==

/// make a new transaction (6 override)
newtransaction
newtransaction {name}

newtransaction {unique_id}
newtransaction {unique_id} {name}

newtransaction {txid}
newtransaction {txid} {name}

response {unique_id}

/// add an input to the transaction. (1 overrides)
addinput {unique_id} {txid} {index}
addinput {unique_id} {txid} {index} {comment}

response {unique_id} {inid}

/// add outputs to the transaction (6 overrides)
/// add fee to transaction
addoutput {unique_id} {amount} {forced|suggested|optional}
addoutput {unique_id} {amount} {forced|suggested|optional} {comment}

// add change address to transaction
addoutput {unique_id} {pubkey}
addoutput {unique_id} {pubkey} {comment}

// add send outputs
addoutput {unique_id} {address} {amount}
addoutput {unique_id} {address} {amount} {comment}

response {unique_id} {outid}

// add many send outputs
addoutputlist {unique_id} [{address},{amount}]

response {unique_id} [{outid}]

/// remove input or outpus (1 override)
remove {unique_id} {unique_id}
remove {unique_id} [{unique_id}]

response {unique_id} droped: {unique_id}
response {unique_id} droped: [{unique_id}]

/// prints out human readable information about the tranaction
shownewtransaction {unique_id} (1 override)

response {unique_id}
in: [{unique_id},{address},{amount},(comment)]
in total: {amount}
out: [{unique_id},{address},{amount},(comment)]
out total: {amount}
fee: {amount}
size: {readytxn bit}
state: {building:ready:done:submitted}

shownewtransaction {txid} (1 override)

response {txid}
in: [{txid},{address},{amount},(comment)]
in total: {amount}
out: [{address},{amount},(comment)]
out total: {amount}
fee: {amount}
size: {readytxn bit}
block: {block number}

/// demote a transaction (1 override)
demotetransaction {unique_id}
demotetransaction {unique_id} {build|ready|done}

response {unique_id} {building|ready|done}

/// exports a binary encoded transition (4 override)
exporttransaction {unique_id}
exporttransaction [unique_id]
exporttransaction {txid}
exporttransaction [txid]

response {binary data}

/// import binary encoded transition(s) (1 override)
inporttransaction {binary data}
inporttransaction [{binary data}]

response [{unique_id}]

/// check and complete ''build'' translation (1 override)
reddytransaction {unique_id}
reddytransaction [{unique_id}]

response [{unique_id}] {has made changes|no changes needed|not enough coins|invalid transaction}

/// sign ''ready'' transaction (6 override)
signtransaction {unique_id}
signtransaction [{unique_id}]

// calls reddytransaction before hand if needed
signtransaction -r {unique_id}
signtransaction -r [{unique_id}]

// sign a pre-signed/partial transaction (signs for owned private keys)
signtransaction -o {unique_id}
signtransaction -o [{unique_id}]

response [{unique_id},{done|failed}]

/// publish a ''done'' transaction to peers (2 override)
// submits all 'done' transactions
submittransaction -a

// submits a single 'done' transaction
submittransaction {unique_id}

// submits a list of 'done' transaction
submittransaction [{unique_id}]

response [{unique_id},{txid}]

/// complete transaction from any stage and publish it (1 override)
completeransaction {unique_id}

response {unique_id} {txid}

/// delete a transaction from local client
droptransaction {unique_id}

responce dropped: {unique_id}

Da2ce7:New Transaction

2011-07-25T19:45:15Z

Da2ce7:

''New Transaction'' is an proposal for a new extendable method of creating transactions. 
Each new transaction is defined by a random ''txnumber'' that should be unique globally. 
Advanced functions, such as transaction scripts, and importing and exporting can appropriately be done using the group of supporting functions.

=== Transaction life-cycle ===
Every New Transaction goes through the following steps. (not always in the same order)

==== Build ====
In this stage, a transaction is being built: 
* Any feature of the transaction may be modified.
* Users can add, remove, any input, output or script.

==== Ready ====
In this stage, only certain features may be modified: 
* Only inputs may be changed. (is this correct, or will past signatures be destroyed if we change them?)
* Any other attribute that doesn't effect the existing signatures.

==== Done ====
In this stage, the transaction is complete, and would be accepted by the network:
* User still can add inputs, however all the outputs have already been fulfilled, these new inputs will be counted as fees.
* After any change, a 'done' transaction gets automatically demoted to 'Ready' state.

==== Submitted ====
In this stage the transaction has been published to the bitcoin network and is in/or is awaiting to be included in a block.

=== Terms ===

''txnumber'' is a random string given to every transaction for identification purposes. 
''pubkey'' is assumed to be owned by the client that preforms the 'readying' of the transition (build > ready states)

'''This entire processing is lazy! Bitcoin will automatically fill-out everything just as it dose at-the-moment with the ''readytransaction'' stage.'''

Please not this draft doesn't include all possible error responses.

== commands: ==

/// make a new transaction (1 override)
newtransaction
newtransaction {name}

response {unique_id}

/// add an input to the transaction. (1 overrides)
addinput {unique_id} {txid} {index}
addinput {unique_id} {txid} {index} {comment}

response {unique_id} {inid}

/// add outputs to the transaction (6 overrides)
/// add fee to transaction
addoutput {unique_id} {amount} {forced|suggested|optional}
addoutput {unique_id} {amount} {forced|suggested|optional} {comment}

// add change address to transaction
addoutput {unique_id} {pubkey}
addoutput {unique_id} {pubkey} {comment}

// add send outputs
addoutput {unique_id} {address} {amount}
addoutput {unique_id} {address} {amount} {comment}

response {unique_id} {outid}

// add many send outputs
addoutputlist {unique_id} [{address},{amount}]

response {unique_id} [{outid}]

/// remove input or outpus (1 override)
remove {unique_id} {unique_id}
remove {unique_id} [{unique_id}]

response {unique_id} droped: {unique_id}
response {unique_id} droped: [{unique_id}]

/// prints out human readable information about the tranaction
shownewtransaction {unique_id} (1 override)

response {unique_id}
in: [{unique_id},{address},{amount},(comment)]
in total: {amount}
out: [{unique_id},{address},{amount},(comment)]
out total: {amount}
fee: {amount}
size: {readytxn bit}
state: {building:ready:done:submitted}

shownewtransaction {txid} (1 override)

response {txid}
in: [{txid},{address},{amount},(comment)]
in total: {amount}
out: [{address},{amount},(comment)]
out total: {amount}
fee: {amount}
size: {readytxn bit}
block: {block number}

/// demote a transaction (1 override)
demotetransaction {unique_id}
demotetransaction {unique_id} {build|ready|done}

response {unique_id} {building|ready|done}

/// exports a binary encoded transition (4 override)
exporttransaction {unique_id}
exporttransaction [unique_id]
exporttransaction {txid}
exporttransaction [txid]

response {binary data}

/// import binary encoded transition(s) (1 override)
inporttransaction {binary data}
inporttransaction [{binary data}]

response [{unique_id}]

/// check and complete ''build'' translation (1 override)
reddytransaction {unique_id}
reddytransaction [{unique_id}]

response [{unique_id}] {has made changes|no changes needed|not enough coins|invalid transaction}

/// sign ''ready'' transaction (6 override)
signtransaction {unique_id}
signtransaction [{unique_id}]

// calls reddytransaction before hand if needed
signtransaction -r {unique_id}
signtransaction -r [{unique_id}]

// sign a pre-signed/partial transaction (signs for owned private keys)
signtransaction -o {unique_id}
signtransaction -o [{unique_id}]

response [{unique_id},{done|failed}]

/// publish a ''done'' transaction to peers (2 override)
// submits all 'done' transactions
submittransaction -a

// submits a single 'done' transaction
submittransaction {unique_id}

// submits a list of 'done' transaction
submittransaction [{unique_id}]

response [{unique_id},{txid}]

/// complete transaction from any stage and publish it (1 override)
completeransaction {unique_id}

response {unique_id} {txid}

/// delete a transaction from local client
droptransaction {unique_id}

responce dropped: {unique_id}

Da2ce7:New Transaction

2011-07-25T19:44:11Z

Da2ce7: updated to unique_id

''New Transaction'' is an proposal for a new extendable method of creating transactions. 
Each new transaction is defined by a random ''txnumber'' that should be unique globally. 
Advanced functions, such as transaction scripts, and importing and exporting can appropriately be done using the group of supporting functions.

=== Transaction life-cycle ===
Every New Transaction goes through the following steps. (not always in the same order)

==== Build ====
In this stage, a transaction is being built: 
* Any feature of the transaction may be modified.
* Users can add, remove, any input, output or script.

==== Ready ====
In this stage, only certain features may be modified: 
* Only inputs may be changed. (is this correct, or will past signatures be destroyed if we change them?)
* Any other attribute that doesn't effect the existing signatures.

==== Done ====
In this stage, the transaction is complete, and would be accepted by the network:
* User still can add inputs, however all the outputs have already been fulfilled, these new inputs will be counted as fees.
* After any change, a 'done' transaction gets automatically demoted to 'Ready' state.

==== Submitted ====
In this stage the transaction has been published to the bitcoin network and is in/or is awaiting to be included in a block.

=== Terms ===

''txnumber'' is a random string given to every transaction for identification purposes. 
''pubkey'' is assumed to be owned by the client that preforms the 'readying' of the transition (build > ready states)

'''This entire processing is lazy! Bitcoin will automatically fill-out everything just as it dose at-the-moment with the ''readytransaction'' stage.'''

Please not this draft doesn't include all possible error responses.

== commands: ==

/// make a new transaction (1 override)
newtransaction
newtransaction {name}

response {unique_id}

/// add an input to the transaction. (1 overrides)
addinput {unique_id} {txid} {index}
addinput {unique_id} {txid} {index} {comment}

response {unique_id} {inid}

/// add outputs to the transaction (6 overrides)
/// add fee to transaction
addoutput {unique_id} {amount} {forced|suggested|optional}
addoutput {unique_id} {amount} {forced|suggested|optional} {comment}

// add change address to transaction
addoutput {unique_id} {pubkey}
addoutput {unique_id} {pubkey} {comment}

// add send outputs
addoutput {unique_id} {address} {amount}
addoutput {unique_id} {address} {amount} {comment}

response {unique_id} {outid}

// add many send outputs
addoutputlist {unique_id} [{address},{amount}]

response {unique_id} [{outid}]

/// remove input or outpus (1 override)
remove {unique_id} {inid or outid}
remove {unique_id} [{inid or outid}]

response {unique_id} droped: {inid or outid}
response {unique_id} droped: [{inid or outid}]

/// prints out human readable information about the tranaction
shownewtransaction {unique_id} (1 override)

response {unique_id}
in: [{unique_id},{address},{amount},(comment)]
in total: {amount}
out: [{unique_id},{address},{amount},(comment)]
out total: {amount}
fee: {amount}
size: {readytxn bit}
state: {building:ready:done:submitted}

shownewtransaction {txid} (1 override)

response {txid}
in: [{txid},{address},{amount},(comment)]
in total: {amount}
out: [{address},{amount},(comment)]
out total: {amount}
fee: {amount}
size: {readytxn bit}
block: {block number}

/// demote a transaction (1 override)
demotetransaction {unique_id}
demotetransaction {unique_id} {build|ready|done}

response {unique_id} {building|ready|done}

/// exports a binary encoded transition (4 override)
exporttransaction {unique_id}
exporttransaction [unique_id]
exporttransaction {txid}
exporttransaction [txid]

response {binary data}

/// import binary encoded transition(s) (1 override)
inporttransaction {binary data}
inporttransaction [{binary data}]

response [{unique_id}]

/// check and complete ''build'' translation (1 override)
reddytransaction {unique_id}
reddytransaction [{unique_id}]

response [{unique_id}] {has made changes|no changes needed|not enough coins|invalid transaction}

/// sign ''ready'' transaction (6 override)
signtransaction {unique_id}
signtransaction [{unique_id}]

// calls reddytransaction before hand if needed
signtransaction -r {unique_id}
signtransaction -r [{unique_id}]

// sign a pre-signed/partial transaction (signs for owned private keys)
signtransaction -o {unique_id}
signtransaction -o [{unique_id}]

response [{unique_id},{done|failed}]

/// publish a ''done'' transaction to peers (2 override)
// submits all 'done' transactions
submittransaction -a

// submits a single 'done' transaction
submittransaction {unique_id}

// submits a list of 'done' transaction
submittransaction [{unique_id}]

response [{unique_id},{txid}]

/// complete transaction from any stage and publish it (1 override)
completeransaction {unique_id}

response {unique_id} {txid}

/// delete a transaction from local client
droptransaction {unique_id}

responce dropped: {unique_id}

Da2ce7:New Transaction

2011-07-25T19:08:50Z

Da2ce7: Changed Input.

''New Transaction'' is an proposal for a new extendable method of creating transactions. 
Each new transaction is defined by a random ''txnumber'' that should be unique globally. 
Advanced functions, such as transaction scripts, and importing and exporting can appropriately be done using the group of supporting functions.

=== Transaction life-cycle ===
Every New Transaction goes through the following steps. (not always in the same order)

==== Build ====
In this stage, a transaction is being built: 
* Any feature of the transaction may be modified.
* Users can add, remove, any input, output or script.

==== Ready ====
In this stage, only certain features may be modified: 
* Only inputs may be changed. (is this correct, or will past signatures be destroyed if we change them?)
* Any other attribute that doesn't effect the existing signatures.

==== Done ====
In this stage, the transaction is complete, and would be accepted by the network:
* User still can add inputs, however all the outputs have already been fulfilled, these new inputs will be counted as fees.
* After any change, a 'done' transaction gets automatically demoted to 'Ready' state.

==== Submitted ====
In this stage the transaction has been published to the bitcoin network and is in/or is awaiting to be included in a block.

=== Terms ===

''txnumber'' is a random string given to every transaction for identification purposes. 
''pubkey'' is assumed to be owned by the client that preforms the 'readying' of the transition (build > ready states)

'''This entire processing is lazy! Bitcoin will automatically fill-out everything just as it dose at-the-moment with the ''readytransaction'' stage.'''

Please not this draft doesn't include all possible error responses.

== commands: ==

/// make a new transaction (1 override)
newtransaction
newtransaction {name}

response {txnumber}

/// add an input to the transaction. (1 overrides)
addinput {txnumber} {txid} {index}
addinput {txnumber} {txid} {index} {comment}

response {txnumber} {inid}

/// add outputs to the transaction (6 overrides)
/// add fee to transaction
addoutput {txnumber} {amount} {forced|suggested|optional}
addoutput {txnumber} {amount} {forced|suggested|optional} {comment}

// add change address to transaction
addoutput {txnumber} {pubkey}
addoutput {txnumber} {pubkey} {comment}

// add send outputs
addoutput {txnumber} {address} {amount}
addoutput {txnumber} {address} {amount} {comment}

response {txnumber} {outid}

// add many send outputs
addoutputlist {txnumber} [{address},{amount}]

response {txnumber} [{outid}]

/// remove input or outpus (1 override)
remove {txnumber} {inid or outid}
remove {txnumber} [{inid or outid}]

response {txnumber} droped: {inid or outid}
response {txnumber} droped: [{inid or outid}]

/// prints out human readable information about the tranaction
shownewtransaction {txnumber} (1 override)

response {txnumber}
in: [{inid},{address},{amount},(comment)]
in total: {amount}
out: [{outid},{address},{amount},(comment)]
out total: {amount}
fee: {amount}
size: {readytxn bit}
state: {building:ready:done:submitted}

shownewtransaction {txid} (1 override)

response {txid}
in: [{inid},{address},{amount},(comment)]
in total: {amount}
out: [{outid},{address},{amount},(comment)]
out total: {amount}
fee: {amount}
size: {readytxn bit}
block: {block number}

/// demote a transaction (1 override)
demotetransaction {txnumber}
demotetransaction {txnumber} {build|ready|done}

response {txnumber} {building|ready|done}

/// exports a binary encoded transition (4 override)
exporttransaction {txnumber}
exporttransaction [txnumber]
exporttransaction {txid}
exporttransaction [txid]

response {binary data}

/// import binary encoded transition(s) (1 override)
inporttransaction {binary data}
inporttransaction [{binary data}]

response [{txnumber}]

/// check and complete ''build'' translation (1 override)
reddytransaction {txnumber}
reddytransaction [{txnumber}]

response [{txnumber}] {has made changes|no changes needed|not enough coins|invalid transaction}

/// sign ''ready'' transaction (6 override)
signtransaction {txnumber}
signtransaction [{txnumber}]

// calls reddytransaction before hand if needed
signtransaction -r {txnumber}
signtransaction -r [{txnumber}]

// sign a pre-signed/partial transaction (signs for owned private keys)
signtransaction -o {txnumber}
signtransaction -o [{txnumber}]

response [{txnumber},{done|failed}]

/// publish a ''done'' transaction to peers (2 override)
// submits all 'done' transactions
submittransaction -a

// submits a single 'done' transaction
submittransaction {txnumber}

// submits a list of 'done' transaction
submittransaction [{txnumber}]

response [{txnumber},{txid}]

/// complete transaction from any stage and publish it (1 override)
completeransaction {txnumber}

response {txnumber} {txid}

/// delete a transaction from local client
droptransaction {txnumber}

responce dropped: {txnumber}

Da2ce7:New Transaction

2011-07-25T18:14:26Z

Da2ce7:

''New Transaction'' is an proposal for a new extendable method of creating transactions. 
Each new transaction is defined by a random ''txnumber'' that should be unique globally. 
Advanced functions, such as transaction scripts, and importing and exporting can appropriately be done using the group of supporting functions.

=== Transaction life-cycle ===
Every New Transaction goes through the following steps. (not always in the same order)

==== Build ====
In this stage, a transaction is being built: 
* Any feature of the transaction may be modified.
* Users can add, remove, any input, output or script.

==== Ready ====
In this stage, only certain features may be modified: 
* Only inputs may be changed. (is this correct, or will past signatures be destroyed if we change them?)
* Any other attribute that doesn't effect the existing signatures.

==== Done ====
In this stage, the transaction is complete, and would be accepted by the network:
* User still can add inputs, however all the outputs have already been fulfilled, these new inputs will be counted as fees.
* After any change, a 'done' transaction gets automatically demoted to 'Ready' state.

==== Submitted ====
In this stage the transaction has been published to the bitcoin network and is in/or is awaiting to be included in a block.

=== Terms ===

''txnumber'' is a random string given to every transaction for identification purposes. 
''pubkey'' is assumed to be owned by the client that preforms the 'readying' of the transition (build > ready states)

'''This entire processing is lazy! Bitcoin will automatically fill-out everything just as it dose at-the-moment with the ''readytransaction'' stage.'''

Please not this draft doesn't include all possible error responses.

== commands: ==

/// make a new transaction (1 override)
newtransaction
newtransaction {name}

response {txnumber}

/// add an input to the transaction. (1 overrides)
addinput {txnumber} {txid} {pubkey}
addinput {txnumber} {txid} {pubkey} {comment}

response {txnumber} {inid}

/// add outputs to the transaction (6 overrides)
/// add fee to transaction
addoutput {txnumber} {amount} {forced|suggested|optional}
addoutput {txnumber} {amount} {forced|suggested|optional} {comment}

// add change address to transaction
addoutput {txnumber} {pubkey}
addoutput {txnumber} {pubkey} {comment}

// add send outputs
addoutput {txnumber} {address} {amount}
addoutput {txnumber} {address} {amount} {comment}

response {txnumber} {outid}

// add many send outputs
addoutputlist {txnumber} [{address},{amount}]

response {txnumber} [{outid}]

/// remove input or outpus (1 override)
remove {txnumber} {inid or outid}
remove {txnumber} [{inid or outid}]

response {txnumber} droped: {inid or outid}
response {txnumber} droped: [{inid or outid}]

/// prints out human readable information about the tranaction
shownewtransaction {txnumber} (1 override)

response {txnumber}
in: [{inid},{address},{amount},(comment)]
in total: {amount}
out: [{outid},{address},{amount},(comment)]
out total: {amount}
fee: {amount}
size: {readytxn bit}
state: {building:ready:done:submitted}

shownewtransaction {txid} (1 override)

response {txid}
in: [{inid},{address},{amount},(comment)]
in total: {amount}
out: [{outid},{address},{amount},(comment)]
out total: {amount}
fee: {amount}
size: {readytxn bit}
block: {block number}

/// demote a transaction (1 override)
demotetransaction {txnumber}
demotetransaction {txnumber} {build|ready|done}

response {txnumber} {building|ready|done}

/// exports a binary encoded transition (4 override)
exporttransaction {txnumber}
exporttransaction [txnumber]
exporttransaction {txid}
exporttransaction [txid]

response {binary data}

/// import binary encoded transition(s) (1 override)
inporttransaction {binary data}
inporttransaction [{binary data}]

response [{txnumber}]

/// check and complete ''build'' translation (1 override)
reddytransaction {txnumber}
reddytransaction [{txnumber}]

response [{txnumber}] {has made changes|no changes needed|not enough coins|invalid transaction}

/// sign ''ready'' transaction (6 override)
signtransaction {txnumber}
signtransaction [{txnumber}]

// calls reddytransaction before hand if needed
signtransaction -r {txnumber}
signtransaction -r [{txnumber}]

// sign a pre-signed/partial transaction (signs for owned private keys)
signtransaction -o {txnumber}
signtransaction -o [{txnumber}]

response [{txnumber},{done|failed}]

/// publish a ''done'' transaction to peers (2 override)
// submits all 'done' transactions
submittransaction -a

// submits a single 'done' transaction
submittransaction {txnumber}

// submits a list of 'done' transaction
submittransaction [{txnumber}]

response [{txnumber},{txid}]

/// complete transaction from any stage and publish it (1 override)
completeransaction {txnumber}

response {txnumber} {txid}

/// delete a transaction from local client
droptransaction {txnumber}

responce dropped: {txnumber}

Da2ce7:New Transaction

2011-07-25T18:13:55Z

Da2ce7: updated intro

''New Transaction'' is an proposal for a new extendable method of creating transactions. 
Each new transaction is defined by a random ''txnumber'' that should be unique globally. 
Advanced functions, such as transaction scripts, and importing and exporting can appropriately be done using the group of supporting functions.

=== Transaction life-cycle ===
Every New Transaction goes through the following steps. (not always in the same order)

==== Build ====
In this stage, a transaction is being built: 
* Any feature of the transaction may be modified.
* Users can add, remove, any input, output or script.

==== Ready ====
In this stage, only certain features may be modified: 
* Only inputs may be changed. (is this correct, or will past signatures be destroyed if we change them?)
* Any other attribute that doesn't effect the existing signatures.

==== Done ====
In this stage, the transaction is complete, and would be accepted by the network:
* User still can add inputs, however all the outputs have already been fulfilled, these new inputs will be counted as fees.
* After any change, a 'done' transaction gets automatically demoted to 'Ready' state.

==== Submitted ====
In this stage the transaction has been published to the bitcoin network and is in/or is awaiting to be included in a block.

=== Terms ===

''txnumber'' is a random string given to every transaction for identification purposes. 
''pubkey'' is assumed to be owned by the client that preforms the 'readying' of the transition (build > ready states)

'''This entire processing is lazy! Bitcoin will automatically fill-out everything just as it dose at-the-moment with the ''readytransaction'' stage.'''

Please not this draft doesn't include all possible error responses.

== commands: ==

/// make a new transaction (1 override)
newtransaction
newtransaction {name}

response {txnumber}

/// add an input to the transaction. (1 overrides)
addinput {txnumber} {txid} {pubkey}
addinput {txnumber} {txid} {pubkey} {comment}

response {txnumber} {inid}

/// add outputs to the transaction (6 overrides)
/// add fee to transaction
addoutput {txnumber} {amount} {forced|suggested|optional}
addoutput {txnumber} {amount} {forced|suggested|optional} {comment}

// add change address to transaction
addoutput {txnumber} {pubkey}
addoutput {txnumber} {pubkey} {comment}

// add send outputs
addoutput {txnumber} {address} {amount}
addoutput {txnumber} {address} {amount} {comment}

response {txnumber} {outid}

// add many send outputs
addoutputlist {txnumber} [{address},{amount}]

response {txnumber} [{outid}]

/// remove input or outpus (1 override)
remove {txnumber} {inid or outid}
remove {txnumber} [{inid or outid}]

response {txnumber} droped: {inid or outid}
response {txnumber} droped: [{inid or outid}]

/// prints out human readable information about the tranaction
shownewtransaction {txnumber} (1 override)

response {txnumber}
in: [{inid},{address},{amount},(comment)]
in total: {amount}
out: [{outid},{address},{amount},(comment)]
out total: {amount}
fee: {amount}
size: {readytxn bit}
state: {building:ready:done:submitted}

shownewtransaction {txid} (1 override)

response {txid}
in: [{inid},{address},{amount},(comment)]
in total: {amount}
out: [{outid},{address},{amount},(comment)]
out total: {amount}
fee: {amount}
size: {readytxn bit}
block: {block number}

/// demote a transaction (1 override)
demotetransaction {txnumber}
demotetransaction {txnumber} {build|ready|done}

response {txnumber} {building|ready|done}

/// exports a binary encoded transition (4 override)
exporttransaction {txnumber}
exporttransaction [txnumber]
exporttransaction {txid}
exporttransaction [txid]

response {binary data}

/// import binary encoded transition(s) (1 override)
inporttransaction {binary data}
inporttransaction [{binary data}]

response [{txnumber}]

/// check and complete ''build'' translation (1 override)
reddytransaction {txnumber}
reddytransaction [{txnumber}]

response [{txnumber}] {has made changes|no changes needed|not enough coins|invalid transaction}

/// sign ''ready'' transaction (6 override)
signtransaction {txnumber}
signtransaction [{txnumber}]

// calls reddytransaction before hand if needed
signtransaction -r {txnumber}
signtransaction -r [{txnumber}]

// sign a pre-signed/partial transaction (signs for owned private keys)
signtransaction -o {txnumber}
signtransaction -o [{txnumber}]

response [{txnumber},{done|failed}]

/// publish a ''done'' transaction to peers (2 override)
// submits all 'done' transactions
submittransaction -a

// submits a single 'done' transaction
submittransaction {txnumber}

// submits a list of 'done' transaction
submittransaction [{txnumber}]

response [{txnumber},{txid}]

/// complete transaction from any stage and publish it (1 override)
completeransaction {txnumber}

response {txnumber} {txid}

/// delete a transaction from local client
droptransaction {txnumber}

responce dropped: {txnumber}

Da2ce7:New Transaction

2011-07-25T15:31:35Z

Da2ce7: added lists for processing

''make new transaction''

''txnumber'' is a random string given to every transaction for identification purposes. 
''pubkey'' is assumed to be owned by the client that preforms the 'readying' of the transition (build > ready states)

=== States: ===
''build'' this state a transaction doesn't need to fulfil any rules. The user just defines what she wants in the transaction. 
''ready'' this state is after a client that has (or knows of the), private keys checks the transaction, checking and adding more inputs or change output if necessary. 
''done'' the transaction has been signed by and all the inputs are vaild. 
''submited'' the transaction has successfully publicly announced.

'''This entire processing is lazy! Bitcoin will automatically fill-out everything just as it dose at-the-moment with the ''readytransaction'' stage.'''

Please not this draft doesn't include all possible error responses.

== commands: ==

/// make a new transaction (1 override)
newtransaction
newtransaction {name}

response {txnumber}

/// add an input to the transaction. (1 overrides)
addinput {txnumber} {txid} {pubkey}
addinput {txnumber} {txid} {pubkey} {comment}

response {txnumber} {inid}

/// add outputs to the transaction (6 overrides)
/// add fee to transaction
addoutput {txnumber} {amount} {forced|suggested|optional}
addoutput {txnumber} {amount} {forced|suggested|optional} {comment}

// add change address to transaction
addoutput {txnumber} {pubkey}
addoutput {txnumber} {pubkey} {comment}

// add send outputs
addoutput {txnumber} {address} {amount}
addoutput {txnumber} {address} {amount} {comment}

response {txnumber} {outid}

// add many send outputs
addoutputlist {txnumber} [{address},{amount}]

response {txnumber} [{outid}]

/// remove input or outpus (1 override)
remove {txnumber} {inid or outid}
remove {txnumber} [{inid or outid}]

response {txnumber} droped: {inid or outid}
response {txnumber} droped: [{inid or outid}]

/// prints out human readable information about the tranaction
shownewtransaction {txnumber} (1 override)

response {txnumber}
in: [{inid},{address},{amount},(comment)]
in total: {amount}
out: [{outid},{address},{amount},(comment)]
out total: {amount}
fee: {amount}
size: {readytxn bit}
state: {building:ready:done:submitted}

shownewtransaction {txid} (1 override)

response {txid}
in: [{inid},{address},{amount},(comment)]
in total: {amount}
out: [{outid},{address},{amount},(comment)]
out total: {amount}
fee: {amount}
size: {readytxn bit}
block: {block number}

/// demote a transaction (1 override)
demotetransaction {txnumber}
demotetransaction {txnumber} {build|ready|done}

response {txnumber} {building|ready|done}

/// exports a binary encoded transition (4 override)
exporttransaction {txnumber}
exporttransaction [txnumber]
exporttransaction {txid}
exporttransaction [txid]

response {binary data}

/// import binary encoded transition(s) (1 override)
inporttransaction {binary data}
inporttransaction [{binary data}]

response [{txnumber}]

/// check and complete ''build'' translation (1 override)
reddytransaction {txnumber}
reddytransaction [{txnumber}]

response [{txnumber}] {has made changes|no changes needed|not enough coins|invalid transaction}

/// sign ''ready'' transaction (4 override)
signtransaction {txnumber}
signtransaction [{txnumber}]

// calls reddytransaction before hand if needed
signtransaction -r {txnumber}
signtransaction -r [{txnumber}]

response [{txnumber},{done|failed}]

/// publish a ''done'' transaction to peers (2 override)
// submits all 'done' transactions
submittransaction -a

// submits a single 'done' transaction
submittransaction {txnumber}

// submits a list of 'done' transaction
submittransaction [{txnumber}]

response [{txnumber},{txid}]

/// complete transaction from any stage and publish it (1 override)
completeransaction {txnumber}

response {txnumber} {txid}

/// delete a transaction from local client
droptransaction {txnumber}

responce dropped: {txnumber}

Da2ce7:New Transaction

2011-07-25T15:10:42Z

Da2ce7: formating

''make new transaction''

''txnumber'' is a random string given to every transaction for identification purposes. 
''pubkey'' is assumed to be owned by the client that preforms the 'readying' of the transition (build > ready states)

=== States: ===
''build'' this state a transaction doesn't need to fulfil any rules. The user just defines what she wants in the transaction. 
''ready'' this state is after a client that has (or knows of the), private keys checks the transaction, checking and adding more inputs or change output if necessary. 
''done'' the transaction has been signed by and all the inputs are vaild. 
''submited'' the transaction has successfully publicly announced.

'''This entire processing is lazy! Bitcoin will automatically fill-out everything just as it dose at-the-moment with the ''readytransaction'' stage.'''

Please not this draft doesn't include all possible error responses.

== commands: ==

/// make a new transaction (1 override)
newtransaction
newtransaction {name}

response {txnumber}

/// add an input to the transaction. (1 overrides)
addinput {txnumber} {txid} {pubkey}
addinput {txnumber} {txid} {pubkey} {comment}

response {txnumber} {inid}

/// add outputs to the transaction (6 overrides)
/// add fee to transaction
addoutput {txnumber} {amount} {forced:suggested:optional}
addoutput {txnumber} {amount} {forced:suggested:optional} {comment}

// add change address to transaction
addoutput {txnumber} {pubkey}
addoutput {txnumber} {pubkey} {comment}

// add send outputs
addoutput {txnumber} {address} {amount}
addoutput {txnumber} {address} {amount} {comment}

response {txnumber} {outid}

// add many send outputs
addoutputlist {txnumber} [{address},{amount}]

response {txnumber} [{outid}]

/// remove input or outpus (1 override)
remove {txnumber} {inid or outid}
remove {txnumber} [{inid or outid}]

response {txnumber} droped: {inid or outid}
response {txnumber} droped: [{inid or outid}]

/// prints out human readable information about the tranaction
shownewtransaction {txnumber} (1 override)

response {txnumber}
in: [{inid},{address},{amount},(comment)]
in total: {amount}
out: [{outid},{address},{amount},(comment)]
out total: {amount}
fee: {amount}
state: {building:ready:done:submitted}

shownewtransaction {txid} (1 override)

response {txid}
in: [{inid},{address},{amount},(comment)]
in total: {amount}
out: [{outid},{address},{amount},(comment)]
out total: {amount}
fee: {amount}
block: {block number}

/// demote a transaction (1 override)
demotetransaction {txnumber}
demotetransaction {txnumber} {build:ready:done}

response {txnumber} {building:ready:done}

/// exports a binary encoded transition (1 override)
exporttransaction {txnumber}
exporttransaction {txid}

response {binary data base 64 (or 58?) encoded}

/// import a binary encoded transition
exporttransaction {binary data base 64 (or 58?) encoded}

response {txnumber}

/// check and complete ''build'' translation
reddytransaction {txnumber}

response {txnumber} {has made changes:no changes needed:not enough coins:invalid transaction}

/// sign ''ready'' transaction
signtransaction {txnumber} (1 override)

// calls reddytransaction before hand if needed
signtransaction -r {txnumber}

response {txnumber} {done:failed}

/// publish a ''done'' transaction to peers
submittransaction {txnumber}

response {txnumber} {txid}

/// complete transaction from any stage and publish it
completeransaction {txnumber}

response {txnumber} {txid}

/// delete a transaction from local client
droptransaction {txnumber}

responce dropped: {txnumber}

Da2ce7:New Transaction

2011-07-25T15:08:49Z

Da2ce7: formating

''make new transaction''

''txnumber'' is a random string given to every transaction for identification purposes. 
''pubkey'' is assumed to be owned by the client that preforms the 'readying' of the transition (build > ready states)

States:
''build'' this state a transaction doesn't need to fulfil any rules. The user just defines what she wants in the transaction. 
''ready'' this state is after a client that has (or knows of the), private keys checks the transaction, checking and adding more inputs or change output if necessary. 
''done'' the transaction has been signed by and all the inputs are vaild. 
''submited'' the transaction has successfully publicly announced.

'''This entire processing is lazy! Bitcoin will automatically fill-out everything just as it dose at-the-moment with the ''readytransaction'' stage.'''

Please not this draft doesn't include all possible error responses.

== commands: ==

/// make a new transaction (1 override)
newtransaction
newtransaction {name}

response {txnumber}

/// add an input to the transaction. (1 overrides)
addinput {txnumber} {txid} {pubkey}
addinput {txnumber} {txid} {pubkey} {comment}

response {txnumber} {inid}

/// add outputs to the transaction (6 overrides)
/// add fee to transaction
addoutput {txnumber} {amount} {forced:suggested:optional}
addoutput {txnumber} {amount} {forced:suggested:optional} {comment}

// add change address to transaction
addoutput {txnumber} {pubkey}
addoutput {txnumber} {pubkey} {comment}

// add send outputs
addoutput {txnumber} {address} {amount}
addoutput {txnumber} {address} {amount} {comment}

response {txnumber} {outid}

// add many send outputs
addoutputlist {txnumber} [{address},{amount}]

response {txnumber} [{outid}]

/// remove input or outpus (1 override)
remove {txnumber} {inid or outid}
remove {txnumber} [{inid or outid}]

response {txnumber} droped: {inid or outid}
response {txnumber} droped: [{inid or outid}]

/// prints out human readable information about the tranaction
shownewtransaction {txnumber} (1 override)

response {txnumber}
in: [{inid},{address},{amount},(comment)]
in total: {amount}
out: [{outid},{address},{amount},(comment)]
out total: {amount}
fee: {amount}
state: {building:ready:done:submitted}

shownewtransaction {txid} (1 override)

response {txid}
in: [{inid},{address},{amount},(comment)]
in total: {amount}
out: [{outid},{address},{amount},(comment)]
out total: {amount}
fee: {amount}
block: {block number}

/// demote a transaction (1 override)
demotetransaction {txnumber}
demotetransaction {txnumber} {build:ready:done}

response {txnumber} {building:ready:done}

/// exports a binary encoded transition (1 override)
exporttransaction {txnumber}
exporttransaction {txid}

response {binary data base 64 (or 58?) encoded}

/// import a binary encoded transition
exporttransaction {binary data base 64 (or 58?) encoded}

response {txnumber}

/// check and complete ''build'' translation
reddytransaction {txnumber}

response {txnumber} {has made changes:no changes needed:not enough coins:invalid transaction}

/// sign ''ready'' transaction
signtransaction {txnumber} (1 override)

// calls reddytransaction before hand if needed
signtransaction -r {txnumber}

response {txnumber} {done:failed}

/// publish a ''done'' transaction to peers
submittransaction {txnumber}

response {txnumber} {txid}

/// complete transaction from any stage and publish it
completeransaction {txnumber}

response {txnumber} {txid}

/// delete a transaction from local client
droptransaction {txnumber}

responce dropped: {txnumber}

Da2ce7:New Transaction

2011-07-25T15:06:05Z

Da2ce7: ease of use

''make new transaction''

''txnumber'' is a random string given to every transaction for identification purposes. 
''pubkey'' is assumed to be owned by the client that preforms the 'readying' of the transition (build > ready states)

States:
''build'' this state a transaction doesn't need to fulfil any rules. The user just defines what she wants in the transaction.
''ready'' this state is after a client that has (or knows of the), private keys checks the transaction, checking and adding more inputs or change output if necessary.
''done'' the transaction has been signed by and all the inputs are vaild.
''submited'' the transaction has successfully publicly announced.

'''This entire processing is lazy! Bitcoin will automatically fill-out everything just as it dose at-the-moment with the ''readytransaction'' stage.'''

Please not this draft doesn't include all possible error responses.

== commands: ==

/// make a new transaction (1 override)
newtransaction
newtransaction {name}

response {txnumber}

/// add an input to the transaction. (1 overrides)
addinput {txnumber} {txid} {pubkey}
addinput {txnumber} {txid} {pubkey} {comment}

response {txnumber} {inid}

/// add outputs to the transaction (6 overrides)
/// add fee to transaction
addoutput {txnumber} {amount} {forced:suggested:optional}
addoutput {txnumber} {amount} {forced:suggested:optional} {comment}

// add change address to transaction
addoutput {txnumber} {pubkey}
addoutput {txnumber} {pubkey} {comment}

// add send outputs
addoutput {txnumber} {address} {amount}
addoutput {txnumber} {address} {amount} {comment}

response {txnumber} {outid}

// add many send outputs
addoutputlist {txnumber} [{address},{amount}]

response {txnumber} [{outid}]

/// remove input or outpus (1 override)
remove {txnumber} {inid or outid}
remove {txnumber} [{inid or outid}]

response {txnumber} droped: {inid or outid}
response {txnumber} droped: [{inid or outid}]

/// prints out human readable information about the tranaction
shownewtransaction {txnumber} (1 override)

response {txnumber}
in: [{inid},{address},{amount},(comment)]
in total: {amount}
out: [{outid},{address},{amount},(comment)]
out total: {amount}
fee: {amount}
state: {building:ready:done:submitted}

shownewtransaction {txid} (1 override)

response {txid}
in: [{inid},{address},{amount},(comment)]
in total: {amount}
out: [{outid},{address},{amount},(comment)]
out total: {amount}
fee: {amount}
block: {block number}

/// demote a transaction (1 override)
demotetransaction {txnumber}
demotetransaction {txnumber} {build:ready:done}

response {txnumber} {building:ready:done}

/// exports a binary encoded transition (1 override)
exporttransaction {txnumber}
exporttransaction {txid}

response {binary data base 64 (or 58?) encoded}

/// import a binary encoded transition
exporttransaction {binary data base 64 (or 58?) encoded}

response {txnumber}

/// check and complete ''build'' translation
reddytransaction {txnumber}

response {txnumber} {has made changes:no changes needed:not enough coins:invalid transaction}

/// sign ''ready'' transaction
signtransaction {txnumber} (1 override)

// calls reddytransaction before hand if needed
signtransaction -r {txnumber}

response {txnumber} {done:failed}

/// publish a ''done'' transaction to peers
submittransaction {txnumber}

response {txnumber} {txid}

/// complete transaction from any stage and publish it
completeransaction {txnumber}

response {txnumber} {txid}

/// delete a transaction from local client
droptransaction {txnumber}

responce dropped: {txnumber}

Da2ce7:New Transaction

2011-07-25T14:49:49Z

Da2ce7: updated

''make new transaction''

''txnumber'' is a random string given to every transaction for identification purposes. 
''pubkey'' is assumed to be owned by the client that preforms the 'readying' of the transition (build > ready states)

States:
''build'' this state a transaction doesn't need to fulfil any rules. The user just defines what she wants in the transaction.
''ready'' this state is after a client that has (or knows of the), private keys checks the transaction, checking and adding more inputs or change output if necessary.
''done'' the transaction has been signed by and all the inputs are vaild.
''submited'' the transaction has successfully publicly announced.

'''This entire processing is lazy! Bitcoin will automatically fill-out everything just as it dose at-the-moment with the ''readytransaction'' stage.'''

Please not this draft doesn't include all possible error responses.

== commands: ==

/// make a new transaction (1 override)
newtransaction
newtransaction {name}

response {txnumber}

/// add an input to the transaction. (1 overrides)
addinput {txnumber} {txid} {pubkey}
addinput {txnumber} {txid} {pubkey} {comment}

response {txnumber} {inid}

/// add outputs to the transaction (6 overrides)
/// add fee to transaction
addoutput {txnumber} {amount} {forced:suggested:optional}
addoutput {txnumber} {amount} {forced:suggested:optional} {comment}

// add change address to transaction
addoutput {txnumber} {pubkey}
addoutput {txnumber} {pubkey} {comment}

// add send outputs
addoutput {txnumber} {address} {amount}
addoutput {txnumber} {address} {amount} {comment}

response {txnumber} {outid}

// add many send outputs
addoutputlist {txnumber} [{address},{amount}]

response {txnumber} [{outid}]

/// remove input or outpus (1 override)
remove {txnumber} {inid or outid}
remove {txnumber} [{inid or outid}]

response {txnumber} droped: {inid or outid}
response {txnumber} droped: [{inid or outid}]

/// prints out human readable information about the tranaction
shownewtransaction {txnumber} (1 override)

response {txnumber}
in: [{inid},{address},{amount},(comment)]
in total: {amount}
out: [{outid},{address},{amount},(comment)]
out total: {amount}
fee: {amount}
state: {building:ready:done:submitted}

shownewtransaction {txid} (1 override)

response {txid}
in: [{inid},{address},{amount},(comment)]
in total: {amount}
out: [{outid},{address},{amount},(comment)]
out total: {amount}
fee: {amount}
block: {block number}

/// demote a transaction (1 override)
demotetransaction {txnumber}
demotetransaction {txnumber} {build:ready:done}

response {txnumber} {building:ready:done}

/// exports a binary encoded transition (1 override)
exporttransaction {txnumber}
exporttransaction {txid}

response {binary data base 64 (or 58?) encoded}

/// import a binary encoded transition
exporttransaction {binary data base 64 (or 58?) encoded}

response {txnumber}

/// check and complete ''build'' translation
reddytransaction {txnumber}

response {txnumber} {has made changes:no changes needed:not enough coins:invalid transaction}

/// sign ''ready'' transaction
signtransaction {txnumber}

response {txnumber} {done:failed}

/// publish a ''done'' transaction to peers
submittransaction {txnumber}
response {txnumber} {txid}

/// delete a transaction from local client
droptransaction {txnumber}

responce dropped: {txnumber}

Da2ce7:New Transaction

2011-07-25T14:35:27Z

Da2ce7: big update

''make new transaction''

''txnumber'' is a random string given to every transaction for identification purposes. 
''pubkey'' is assumed to be owned by the client that preforms the 'readying' of the transition (build > ready states)

States:
''build'' this state a transaction doesn't need to fulfil any rules. The user just defines what she wants in the transaction.
''ready'' this state is after a client that has (or knows of the), private keys checks the transaction, checking and adding more inputs or change output if necessary.
''done'' the transaction has been signed by and all the inputs are vaild.
''submited'' the transaction has successfully publicly announced.

Please not this draft doesn't include all possible error responses.

== commands: ==

/// make a new transaction (1 override)
newtransaction
newtransaction {name}

response {txnumber}

/// add an input to the transaction. (1 overrides)
addinput {txnumber} {txid} {pubkey}
addinput {txnumber} {txid} {pubkey} {comment}

response {txnumber} {inid}

/// add outputs to the transaction (6 overrides)
/// add fee to transaction
addoutput {txnumber} {amount} {forced:suggested:optional}
addoutput {txnumber} {amount} {forced:suggested:optional} {comment}

// add change address to transaction
addoutput {txnumber} {pubkey}
addoutput {txnumber} {pubkey} {comment}

// add send outputs
addoutput {txnumber} {address} {amount}
addoutput {txnumber} {address} {amount} {comment}

response {txnumber} {outid}

// add many send outputs
addoutputlist {txnumber} [{address},{amount}]

response {txnumber} [{outid}]

/// remove input or outpus (1 override)
remove {txnumber} {inid or outid}
remove {txnumber} [{inid or outid}]

response {txnumber} droped: {inid or outid}
response {txnumber} droped: [{inid or outid}]

/// prints out human readable information about the tranaction
shownewtransaction {txnumber} (1 override)

response {txnumber}
in: [{inid},{address},{amount},(comment)]
out: [{outid},{address},{amount},(comment)]
fee: {amount}
state: {building:ready:done:submitted}

shownewtransaction {txid} (1 override)

response {txid}
in: [{inid},{address},{amount},(comment)]
out: [{outid},{address},{amount},(comment)]
fee: {amount}
block: {block number}

/// demote a transaction (1 override)
demotetransaction {txnumber}
demotetransaction {txnumber} {build:ready:done}

response {txnumber} {building:ready:done}

/// exports a binary encoded transition (1 override)
exporttransaction {txnumber}
exporttransaction {txid}

response {binary data base 64 (or 58?) encoded}

/// import a binary encoded transition
exporttransaction {binary data base 64 (or 58?) encoded}

response {txnumber}

/// check and complete ''build'' translation
reddytransaction {txnumber}

response {txnumber} {has made changes:no changes needed:not enough coins:invalid transaction}

/// sign ''ready'' transaction
signtransaction {txnumber}

response {txnumber} {done:failed}

/// publish a ''done'' transaction to peers
submittransaction {txnumber}
response {txnumber} {txid}

/// delete a transaction from local client
droptransaction {txnumber}

responce dropped: {txnumber}

Da2ce7:New Transaction

2011-07-25T11:43:48Z

Da2ce7: spelling

''make new transaction''

commands:

newtransaction ({name})
response: {txnumber}

addinput {txnumber} {txid} {pubkey} ({comment})
response: {txnumber} {inid}

addoutput {txnumber} {address} {amount} ({comment})
response: {txnumber} {outid}

addoutputlist {txnumber} [{address},{amount}]
response: {txnumber} [{outid}]

remove: {txnumber} [inid] [{outid}]
response: {txnumber} droped: [{inid}] [{outid}]

addtxfee {txnumber} {amount} {forced:suggested:optional}

setnewtransaction {txnumber} {building:ready:done}
response: {txnumber} {building:ready:done:submitted}

shownewtransaction {txnumber}
response: {txnumber} in: [{address},{amount}] out: [{address},{amount}] fee: {txid} {amount} state: {building:ready:done:submitted}

submitnewtransaction {txnumber}
response: {txnumber} {txid}

clearnewtransaction {txnumber}
responce: dropped: {txnumber}

Da2ce7:New Transaction

2011-07-25T11:41:11Z

Da2ce7: fixed

''make new transaction''

commands:

newtransction ({name})
response: {txnumber}

addinput {txnumber} {txid} {pubkey} ({comment})
response: {txnumber} {inid}

addoutput {txnumber} {address} {amount} ({comment})
response: {txnumber} {outid}

addoutputlist {txnumber} [{address},{amount}]
response: {txnumber} [{outid}]

remove: {txnumber} [inid] [{outid}]
response: {txnumber} droped: [{inid}] [{outid}]

addtxfee {txnumber} {amount} {forced:suggested:optional}

setnewtransation {txnumber} {building:ready:done}
response: {txnumber} {building:ready:done:submitted}

shownewtransation {txnumber}
response: {txnumber} in: [{address},{amount}] out: [{address},{amount}] fee: {txid} {amount} state: {building:ready:done:submitted}

submitnewtransation {txnumber}
response: {txnumber} {txid}

clearnewtransaction {txnumber}
responce: dropped: {txnumber}

Da2ce7:New Transaction

2011-07-25T11:38:41Z

Da2ce7: First

''make new transaction''

commands:

== buildnewtransction {name} ==
response: {txnumber}

== addinput {txnumber} {txid} {pubkey} ({comment}) ==
response: {txnumber} {inid}

== addoutput {txnumber} {address} {amount} ({comment}) ==
response: {txnumber} {outid}

== addoutputlist {txnumber} [({address},{amount}] ==
response: {txnumber} [{outid}]

== remove: {txnumber} [inid] [{outid}] ==
response: {txnumber} droped: [{inid}] [{outid}]

== addtxfee {txnumber} {amount} {forced:suggested:optional} ==

== setnewtransation {txnumber} {building:ready:done} ==
response: {txnumber} {building:ready:done:submitted}

== shownewtransation {txnumber} ==
response: {txnumber} in: [{address},{amount}] out: [{address},{amount}] fee: {txid} {amount} state: {building:ready:done:submitted}

== submitnewtransation {txnumber} ==
response: {txnumber} {txid}

== clearnewtransaction {txnumber} ==
responce: dropped: {txnumber}

Da2ce7:New Transaction

2011-07-25T11:36:07Z

Da2ce7: Make New Transaction

''make new transaction''

commands:

== buildnewtransction {name} ==
response: {txnumber}

== addinput {txnumber} {txid} {pubkey} ({comment}) ==
response: {txnumber} {inid}

== addoutput {txnumber} {address} {amount} ({comment}) ==
response: {txnumber} {outid}

== addoutputlist {txnumber} list:({address} {amount}) ==
response: {txnumber} list:{outid}

== remove: {txnumber} list:{inid} list:{outid} ==
response: {txnumber} droped: list:{inid} list:{outid}

== addtxfee {txnumber} {amount} {forced:suggested:optional} ==

== setnewtransation {txnumber} {building:ready:done} ==
response: {txnumber} {building:ready:done:submitted}

== shownewtransation {txnumber} ==
response: {txnumber} in: list:({pubkey} {amount}) out: list:({address} {amount}) fee: {txid} {amount} state: {building:ready:done:submitted}

== submitnewtransation {txnumber} ==
response: {txnumber} {txid}

== clearnewtransaction {txnumber} ==
responce: dropped: {txnumber}

NewSendCoins

2011-07-21T22:32:11Z

Da2ce7: /* NewSendCoins */

Proposal for an updated, more feature-full 'sendcoins/sendmany' command.

This command requires a confirmation or else it will be forgotten on the next NewSendCoins request.

== NewSendCoins ==

''Request'' 
newsendcoins <send list{Address, Amount}>, <fee> (optional)

''Reply'' 
newsendcoins <status:good|warning|error>, <in list{Private Key, Amount}>, <out list{Address or Private Key, Amount}>, <fee>, <error/warning text>, <tx id>

''Confirmation'' 
newsendcoins <tx id>, <confirm, reject>

NewSendCoins

2011-07-21T22:31:32Z

Da2ce7: Lets See what ppl think!?

Proposal for an updated, more feature-full 'sendcoins/sendmany' command.

This command requires a confirmation or else it will be forgotten on the next NewSendCoins request.

== NewSendCoins ==

''Request''
newsendcoins <send list{Address, Amount}>, <fee> (optional)

''Reply''
newsendcoins <status:good|warning|error>, <in list{Private Key, Amount}>, <out list{Address or Private Key, Amount}>, <fee>, <error/warning text>, <tx id>

''Confirmation''
newsendcoins <tx id>, <confirm, reject>

Securing your wallet

2011-06-29T12:47:30Z

Da2ce7:

==Introduction==

Wallet security can be broken down into two independent goals:
# Protecting your wallet against loss.
# Protecting your wallet against theft.

In the case that your current wallet hasn't been protected adequately (e.g. put online with a weaker password):
# Making a new secure wallet, using appropriate long-term protection.

''For a brief overview see also: [[Wallet Security Dos and Don'ts (Windows)|Wallet Security Dos and Don'ts]]''

==Technical Background==

Bitcoin transactions send Bitcoins to a specific public key. A Bitcoin address is an encoded hash of a public key. In order to use received Bitcoins, you need to have the private key matching the public key you received with. This is sort of like a super long password associated with an account (public key). Your Bitcoin wallet contains all of the private keys necessary for spending your received transactions. If you delete your wallet without a backup, then you no longer have the authorization information necessary to claim your coins, and the coins associated with those keys are lost forever.

The wallet contains a pool of queued keys. By default there are 100 keys in the [[key pool]]. The size of the pool is configurable using the "-keypool" command line argument. When you need an address for whatever reason (send, “new address”, generation, etc.), the key is not actually generated freshly, but taken from this pool. A brand new address is generated to fill the pool back to 100. So when a backup is first created, it has all of your old keys plus 100 unused keys. After sending a transaction, it has 99 unused keys. After a total of 100 new-key actions, you will start using keys that are not in your backup. Since the backup does not have the private keys necessary for authorizing spends of these coins, restoring from the old backup will cause you to lose Bitcoins.

Creating a new address generates a new pair of public and private keys, which are added to your wallet. Each keypair is mostly random numbers, so they cannot be known prior to generation. If you backup your wallet and then create more than 100 new addresses, the keypair associated with the newest addresses will not be in the old wallet because the new keypairs are only known after creating them. Any coins received at these addresses will be lost if you restore from the backup.

The situation is made somewhat more confusing because the receiving addresses shown in the UI are not the only keys in your wallet. Each Bitcoin generation is given a new public key, and, more importantly, each sent transaction also sends some number of Bitcoins back to yourself at a new key. When sending Bitcoins to anyone, you generate a new keypair for yourself and simultaneously send Bitcoins to your new public key and the actual recipient's public key. This is an anonymity feature – it makes tracking Bitcoin transactions much more difficult.

So if you create a backup, do more than 100 things that cause a new key to be used, and then restore from the backup, some Bitcoins will be lost. Bitcoin has not deleted any keys (keys are never deleted) – it has created a new key that is not in your old backup and then sent Bitcoins to it.

== Making a new wallet ==

In the case that a wallet has been distributed, or stored, in a (real or potential) compromised state, it is wise to create a new wallet and transfer the full balance of Bitcoins to an address contained only in the newly created wallet.

For example, this will be necessary if one created a wallet with a password of 12 characters, as suggested. However a few years have passed and the wallet is now more easily compromised. Just re-encrypting isn't secure. One needs to make a new wallet and make the old wallet worthless (spending the funds to the new wallet).

==Making a secure workspace==

===Linux===

The first step is to make a [http://www.howtogeek.com/howto/ubuntu/add-a-user-on-ubuntu-server/ new user,] so run:

<code>adduser new_user_name</code>

as root. When you get to the prompt 'Enter the new value, or press ENTER for the default', just keep hitting ENTER.

Then switch user to the new user. To get to the new user you can use the switch user icon for your system, which on Ubuntu is in the 'System/Quit' screen, or if there is no switch icon on your system you can log out and log back in as the new user. Then click on a folder in the new user to display the file browser, then keep going up folders until you see the new user home directory, then right click to bring up the Properties dialog, then click on the Permissions tab, then in the Others section, set the folder access to None.

For secure browsing, open Firefox, and then go into the Edit menu and click Preferences. Starting from the left, click on the General tab, and in the 'Startup/When Firefox starts' pop up menu, choose 'Show a Blank Page'. Then click on the Content tab, and deselect 'Load images automatically' and deselect 'Enable Javascript'. Then click on the Privacy tab, and in the 'History/Firefox will' pop up menu, choose 'Never remember history'. Then click on the Security tab, and in the Passwords section, deselect 'Remember passwords for sites' and deselect 'Use a master password'. Then click on the Advanced tab, then click on the Update tab, and then in the 'Automatically check for updates to' section, deselect 'Add-ons' and 'Search Engines'.

When javascript is disabled, the [http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.3.23/bitcoin-0.3.23-linux.tar.gz/download linux download page] will not download automatically, so you'll have to click on the 'direct link' part of the "Problems with the download? Please use this 'direct link' or try another mirror." line.

After you've made your secure new user, to maintain security you should use it only for bitcoin.

It's also a good idea to encrypt the Home directory of whatever user you run Bitcoin under using ecryptfs-utils. To do this:
# If the Home directory is not empty you should back it up first, by just copying the data to an external drive or something.
# install ecryptfs-utils (on Ubuntu: sudo apt-get install ecryptfs-utils)
# log out of X (graphical system) and press Ctrl+Alt+F1 to login to the command shell (you must be logged out or some files will be open and the tool won't be able to encrypt your data)
# change directory to something that's not in your home folder (ex: cd / )
# run the migration tool (on Ubuntu: sudo ecryptfs-migrate-home -u username)
# if it's successful, you can now press ALT+F8 to go back to the GUI and login
# run 'ecryptfs-unwrap-passphrase' and '''WRITE DOWN OR SAVE THE CODE IT RETURNS''' because you will need it if you ever have to pull your data off while the OS is not working. (You can run it again later if you need to, but run it now so that you can get your data if your Linux install gets botched.)
# run 'ecryptfs-setup-swap' to encrypt your swap partition (the encrypted folder data is not encrypted while it's in memory, and so if it's ever sent to the swap partition it can be stolen from there unless that too is encrypted - be aware that this will mean you cannot use Hibernate anymore, as the bootloader won't be able to restore the hibernation data)
(instructions from [http://bodhizazen.net/Tutorials/Ecryptfs/#Migrate])

===Mac===

=====Backup all data (500MB)=====
Follow these instructions to backup all the bitcoin data (wallet and block chains) to an encrypted disk image.
# Open Disk Utility
# Click New Image and choose 500MB, 128-bit or 256-bit (faster or more secure) encryption and single partition.
# Save it somewhere you won't lose it (like your Wuala, Dropbox, Strongspace or whatever)
# Choose a safe and strong password
# Move everything from ~/Library/Application Support/Bitcoin/ to the image
# Symlink it back so the app would be able to use it
:::ln -s /Volumes/Bitcoin ~/Library/Application Support/Bitcoin

Don't forget to mount your image before using Bitcoin and unmount after quitting it.

=====Backup just wallet.dat (40MB)=====
Follow these instructions to backup just the wallet.dat file. This results in a smaller disk image, but it's more complicated to do.
# Open Disk Utility
# Click New Image and choose 40MB, 128-bit or 256-bit (faster or more secure) encryption and single partition.
# Save it somewhere you won't lose it (like your Wuala, Dropbox, Strongspace or whatever)
# Choose a safe and strong password
# Move your wallet.dat file to the image
# Symlink it back so the app would be able to use it
:::ln -s /Volumes/Bitcoin/wallet.dat ~/Library/Application Support/Bitcoin/wallet.dat

[[File:MountWalletAndLauchnBitcoin_OSX_Automator.png|thumbnail|150px|Mount Wallet and launch Bitcoin]]
Don't forget to mount your image before using Bitcoin and unmount after quitting it.

'''Note''': If you start the Bitcoin application without having the image mounted, the application will overwrite your symlink with a new wallet. If that happens, don't panic. Just delete the new wallet.dat, mount the image, and recreate the symlink like above.

'''Automation''': You can create a small application using [http://en.wikipedia.org/wiki/Automator_%28software%29 Automator] (included in OS X) to automatically mount the wallet and then launch Bitcoin App. See the Screenshot on how to do this.

If one ''doesn't'' want to use encrypted Disk images, then a '''small shell script''' can be used instead that takes care of decrypting the wallet, launching bitcoin client, and encrypting it after the client exits. This script works on both OSX and Linux: [http://lorelei.kaverit.org/bitcoin.sh bitcoin-launch-script]

===Windows===

If you are using Windows XP or Windows 7, you can keep your wallet on an encrypted disk image created by third-party software, such as [http://www.truecrypt.org/ TrueCrypt] (open source) or [http://www.jetico.com/encryption-bestcrypt/ Jetico BestCrypt] (commercial). You can probably do the same with Windows Vista (but why would you use that?) or Windows 2000.

'''NOTE:''' You should configure BitCoin in this manner only on computers where you use BitCoin, but do not use that computer to mine. For example, this is a good configuration for a notebook or tablet computer.

Assuming that you have installed the Windows BitCoin client and run it at least once, the process is described below.

To mount the BitCoin data directory on an encrypted drive
<ol start=1 type=1>
<li>Use the third-party disk image encryption program of your choice to create and mount an encrypted disk image of at least 100 MB in size.</li>
<li>Locate the BitCoin data directory, and copy the directory with all contents to the encrypted drive.
For help finding this directory, see [[Securing_your_wallet#Locating_BitCoin_s_data_directory|Locating BitCoin's Data Directory]].</li>
<li>Create a Windows shortcut that starts BitCoin with the <code>-datadir</code> parameter and specifies the encrypted drive and directory.
For example, if you installed Bitcoin in the default directory, mounted your BitCoin encrypted drive as <code>E:\</code>, and stored your BitCoin data directory on it as <code>Bitcoin</code>, you would type the following command as the shortcut Target:
<blockquote><code>C:\Program Files\Bitcoin\bitcoin.exe -datadir=E:\Bitcoin</code></blockquote></li>
<li>Open BitCoin's settings and configure it NOT to start automatically when you start Windows.
This is to allow you to mount the BitCoin encrypted disk image before starting BitCoin.</li>
<li>Shut down BitCoin, and then restart it from the new shortcut.</li>
</ol>

After doing this, any time you want to use BitCoin, you must first mount the BitCoin encrypted disk image using the same drive designation, and then run BitCoin from the shortcut that you created, so that it can find its data and your wallet. :-)

== Locating BitCoin's data directory ==

The [[data directory]] is the location where Bitcoin's data files are stored, including the wallet data file.

=== Windows ===

Go to Start -> Run (or press WinKey+R) and run this:

explorer %APPDATA%\BitCoin

BitCoin's data folder will open. For most users, this is the following locations:

C:\Documents and Settings\YourUserName\Application data\BitCoin (XP)

C:\Users\YourUserName\Appdata\Roaming\BitCoin (Vista and 7)

"AppData" and "Application data" are hidden by default.

=== Linux ===

By default BitCoin will put its data here:

~/.bitcoin/

You need to do a "ls -a" to see directories that start with a dot.

If that's not it, you can do a search like this:

find / -name wallet.dat -print 2>/dev/null

=== Mac ===

By default BitCoin will put its data here:

~/Library/Application Support/Bitcoin/

==Backup==

'''Note''': I would strongly recommend against using Dropbox to back up your Bitcoin data due to [http://en.wikipedia.org/wiki/Dropbox_(service)#Criticism security concerns] such as:
# the fact that they store your encryption key (meaning that a disgruntled Dropbox employee or an attacker who gained access to the system could decrypt your Dropbox data and steal your Bitcoins)
# the fact that the Dropbox client only needs a password for the first login. After it authenticates once, the server assigns it a token which it uses to show that, at one time, its user knew the password rather than sending the actual password (meaning that if you ever use the Dropbox client on another PC, that PC's users can access your Dropbox - even if you change your password - and can steal your Bitcoins or get a virus that will steal your Bitcoins).

For these reasons, I personally prefer to use Wuala, which does not store your encryption key and requires a password each time (the client can be set to remember your password, but the server will check each time to make sure that the client is sending the correct password). Like Dropbox, the basic, lowest-storage-space account with Wuala is free of charge, and coincidentally, Wuala [http://www.wuala.com/en/bitcoin is experimenting with allowing users to pay for "upgraded" plans using Bitcoin.]

In fact, whether you use Dropbox as your backup or not, use what Steve Gibson calls "pre-Internet encryption" (which he actually [http://itknowledgeexchange.techtarget.com/security-corner/cloud-security-and-privacy-do-they-exist/ discussed in the context of Dropbox's security concerns]) and use some form of encryption on the files before you back them up, just in case someone other than yourself ever gains access to that backup. Make sure to pick a password that's memorable but secure.

The only file you need to back up is "wallet.dat". Ensure that BitCoin is closed, copy this file somewhere else, encrypt it, and put it somewhere safe. Ideally, you would put this file in two places: one nearby, and one 100+ miles away.

You can use the [[api|backupwallet]] JSON-RPC command to back up without shutting down Bitcoin.

=== General Solutions ===

Your wallet.dat file is not encrypted by BitCoin. Anyone who can access it can easily steal all of your coins. Use one of these encryption programs if there is any chance someone might stumble upon your wallet.
* [http://www.7-zip.org/ 7-zip] - Supports strongly-encrypted archives.
* [http://www.axantum.com/axcrypt/ AxCrypt]
* [http://lrzip.kolivas.org lrzip] - Compression software for Linux and OSX that supports very high grade password protected encryption
* [http://www.truecrypt.org/ TrueCrypt] - Volume-based on-the-fly encryption (for advanced users)
* [http://www.rarlab.com/ WinRar] - Commonly used archive software that supports verification records and encryption.

There is also a list of [[OpenSourceEncryptionSoftware|open source encryption software.]]

There is also a method to Print out and encrypt your Wallet.dat as a special barcode. See details here: [[WalletPaperbackup]]

==== Password Strength ====
Brute-force password cracking has come a long distance, a previously thought secure password of random [a-Z] [0-9] [!-~] of 8 characters long can be trivially solved now (using appropriate hardware)... The recommended length is '''at least''' 12 characters long. You can also use a multi-word password. [http://www.baekdal.com/tips/password-security-usability The Usability of Passwords]

However, simply using dictionary words is also insecure as it opens you up to a dictionary attack. If you use dictionary words, be sure to throw random symbols and numbers in the mix as well.

A good way to create secure but easy-to-remember passwords is to pick a password (ex: d0g) and pad it with a good number of repeated characters afterward (such as 10 $ signs - so d0g becomes d0g$$$$$$$$$$) - this is just as cryptographically secure as a random password of equal length so long as the attacker does not know which symbol you are following your "word" with and how many times it is repeated. ([https://www.grc.com/haystack.htm source])

If you use keyfiles in addition to a password, it is unlikely that your encrypted file can ever be cracked using brute force methods, even 10 years from now when even a 12 character password might be too short.

Assume that any encrypted files you store online (eg. gmail, Dropbox) will be stored somewhere forever and can never be erased.

===== Chooseing Your Password =====
Make sure you pick at least one character in each group: 

Lowercase: abcdefghijklmnopqrstuvwxyz
Uppercase: ABCDEFGHIJKLMNOPQRSTUVWXYZ
Number: 1234567890
Symbol: `~!@#$%^&*()-_=+\|[{]};:'",<.>/? (space)

09 char = insecure
10 char = low security
11 char = medium security
12 char = good security (good enough for your wallet)
13 char = v.good enough for anything.

==== Storage of Archive ====
One of the most simple methods for storing a appropriately '''encrypted''' archive of your wallet.dat file is to send the archive as an email attachment to your own e-mail address. Services like gmail.com use very comprehensive distributed networks that make the loss of data very unlikely. One can even obfuscate the name of the files within the archive, and name the archive something less inviting, such as: 'personal notes' or 'car insurance'.

Another solution is to use a file storage service like [http://www.wuala.com/bitcoin Wuala] ( encrypted, [http://www.bitcoin.org/smf/index.php?topic=5817.0 instructions]), [http://www.dropbox.com Dropbox] and [http://en.wikipedia.org/wiki/Comparison_of_online_backup_services others], including the more secure [http://www.spideroak.com SpiderOak].

=== Linux solution ===

Linux users can setup cron by running 'crontab -e' and adding this line:

01 */1 * * * /usr/local/bin/backupwallet.sh

This cron line runs backupwallet.sh at the 01 minute of every hour. Remember to add a newline after the last line of the crontab file, or else the last line won't run.

backupwallet.sh:

#!/bin/bash

TS=$(date "+%Y%m%d-%H-%M")
WALLET=/tmp/wallet${TS}
WALLET_E=/tmp/wallet${TS}.crypt

if
echo -n making backup...
bitcoind backupwallet $WALLET
<nowiki>[[ ! -s "$WALLET" ]]</nowiki>
then echo failed
elif
echo done
echo -n encrypting....
! gpg -r myusername --output $WALLET_E --encrypt $WALLET
then echo failed
elif
echo done
echo -n copying to distant server...
! scp $WALLET_E user@myserver.org:~/wallets/
then echo failed
else echo done
fi

rm -f $WALLET $WALLET_E

The shell script:

* Calls bitcoind backupwallet to create a time/date-stamped wallet.
* GPG encrypts the wallet with your public key.
* Copies the result to a backup location.

[[Category:Technical]]

==Restore==

Assuming your backup is recent enough that you haven't used up all of your key pool... restoring a wallet to a new (or old) location and rescanning the block chain should leave you with all your coins. Just follow these steps:
* Quit bitcoin(d).
* Copy your backed up wallet.dat into your bitcoin profile directory.
* If copying into existing profile, delete file ''blkindex.dat'' and ''blk0001.dat'' to make the client re-scan the block chain.
And you'll be good as new.

==Erasing Plain Text Wallets==

A good practice is to keep at least two wallets, one as a "current account" for everyday transactions and one as a "savings account" where you store the majority of your Bitcoins.

The "savings account" wallet should be backed up in encrypted form only and all plaintext copies of this wallet should be erased. In case someone gains unauthorised access to your computer (either by physically stealing it or by exploiting a system vulnerability via the internet), they will only be able to spend the coins in your "current account" wallet.

In most operating systems, including Windows, Linux, and Mac OS X, simply deleting a wallet.dat file will ''not'' generally destroy it. It is likely that advanced tools can still be used to recover the wallet.dat file, even after it has been deleted.

The Linux '''shred''' command can be used to overwrite the wallet file with random data prior to deleting; this particular copy of the file will then be practically impossible to recover. Using shred (and similar tools on Windows) however does not guarantee that still other copies don't exist somewhere hidden on your HD. That will depend on your system configuration and what packages you have installed. Some system restore and backup tools, for instance, create periodic snapshots of your filesystem, duplicating your wallet.dat.

In Mac OS, the equivalent of '''shred''' is '''srm''' (introduced in Leopard). Using the Finder to remove files, clicking "Secure Empty Trash" in the Finder menu will shred the contents of the trash can. As with any OS this doesn't guarantee that there are not other copies elsewhere on your system.

For Windows, the built-in command ''cipher /W'' will shred all previously-deleted files. [http://www.cylog.org/utilities/cybershredder.jsp CyberShredder] can securely deleted individual files.

==eWallet==

Storing bitcoins with an [[eWallet]] provider incurs risks as well. Basically you grant the third party, in this case eWallet, full access to your wallet.

==See Also==

* [[Data directory]]
* [http://startbitcoin.com/how-to-create-a-secure-bitcoin-wallet/ Secure Bitcoin Wallet Tutorial]

[[de:Sichere deine Geldbörse]]
[[zh-cn:保护你的钱包]]

Software

2011-06-28T13:55:23Z

Da2ce7: Added trade Data

List of Bitcoin-related software. See also [[:Category:Software|Category:Software]].

==Bitcoin clients==
Bitcoin clients:
*[[Original Bitcoin client|Bitcoin client]] - standard Bitcoin client, recommended for installation
*[[bitcoind]] - GUI-less version of the standard Bitcoin client, providing [[API reference (JSON-RPC)|JSON-RPC]] interface (see also -server option of the standard client)
Frontends to bitcoind:
*[[BitcoinApp]] - RPC client for iOS devices (iPhone, iPad, iPodTouch)
*[[Bitcoiner]] - Java RPC client (Android)
*[[Bitcoin-js-remote]] - JavaScript RPC client, support for QR codes
*[[Python Bitcoinclient]] - Python RPC client
*[[Spesmilo]] - Python/PySide RPC client
*[[Bitcoin-python]] - Python API
*[[Java Bitcoin Client]] - Java API
Alternative, experimental implementations:
*[[BitDroid]] - Java client
*[[Bitdollar]] - C++/Qt client, unstable beta version
*[[BitCoinJ]] - Java client by Google, early development stage
*[[Freecoin]] - C++ client, supports alternative currencies like [[Beertoken]]
*[[Pycoin]] - Python client
*[[QBitcoin]] - C++/Qt client, unfinished

==Bitcoin Trade Data==
*[[Bitcoin Charts]] - Html website that has trading data for virtual all the bitcoin markets.
*[[Bitcoinity]] - Html Ajax website that shows a live feed of [[MtGox]], [[TradeHill]], and [[BitMarket]].
*[[MtGoxLive]] - Html website that shows a live fee of [[MtGox]] trade data in an innovative chart form. (Must Use Chrome)

==Bitcoin software==

Web interfaces for merchants:
*[[MyBitcoin]] - Buy Now button to insert on websites
*[[Btceconomy]] - a JavaScript widget listing items for sale
*[[Javascript Bitcoin Converter]] - currency conversion

Web apps (opensource):
*[[Bitcoin Central]] - currency exchange
*[[Bitcoin Poker Room]] - poker site

Browser extensions:
*[[Bitcoin Extension]] - check balance and send bitcoins (Chrome)
*[[Bitcoin Ticker]] - monitoring price (Chrome)
*[[Bitcoin Prices (extension)]] - monitoring price (Firefox)
*[[Bitcoin Tool]] - recognizes Bitcoin addresses on websites (Firefox, Chrome, IE)

PC apps:
*[[BTConvert]] - currency conversion
*[[Sierra Chart MtGox Bridge]] - real-time charting
*[[BitTicker]] - monitoring price (Mac OS X)
*[[ToyTrader]] - a command line trading tool for [[MtGox]]

Mobile apps:
*[[Bitcoin Alert]] - monitoring price (Android)
*[[BitcoinX]] - monitoring price (Android)
*[[BtcMobile]] - monitoring price and mining pool statistics (iPhone/iPad, Android)
*[[Miner Status]] - monitoring miner status (Android)
*[[SMS Bitcoins]] - transactions by SMS
*[[Bitcoin Wallet Balance]] - view your balance in real time on your android phone

Other device apps:
*[[Zen Cart Bitcoin Payment Module]] - a payment module that interacts with bitcoind for the Zen Cart eCommerce shopping chart

Operating systems:
*[[LinuxCoin]] - a lightweight Debian-based OS, with the Bitcoin client and GPU mining software

Mining apps:
*[[Poclbm]] - Python/OpenCL GPU miner ([[Poclbm-gui|GUI]])
*[[Poclbm-mod]] - more efficient version of [[Poclbm]] ([[Poclbm-mod-gui|GUI]])
*[[DiabloMiner]] - Java/OpenCL GPU miner ([[DiabloMiner.app|MAC OS X GUI]])
*[[RPC Miner]] - remote RPC miner ([[RPCminer.app|MAC OS X GUI]])
*[[Phoenix miner]] - miner
*[[Cpu Miner]] - miner
*[[Ufasoft miner]] - miner
*[[Pyminer]] - Python miner, reference implementation
*[[Remote miner]] - mining pool software
*[[Poold]] - mining pool software
*[[Open Source FGPA Bitcoin Miner]] - a miner that makes use of an FPGA Board

Utilities, libraries, and interfaces:
*[[Bitcointools]] - a set of Python tools accessing the transaction database and the wallet
*[[Finance::MtGox]] - a Perl module which interfaces with the Mt. Gox API
*[[BitcoinCrypto]] - a lightweight Bitcoin crypto library for Java/Android
*[[Bitcoin Dissector]] - a wireshark dissector for the bitcoin protocol

Lists of software:
*[[BitGit]] - list of Bitcoin-related opensource projects hosted at Git

Developer resources:
*[[:Category:Developer|Category:Developer]]
*[[:Category:Technical|Category:Technical]]
*[[Original Bitcoin client/API calls list]]
*[[API reference (JSON-RPC)]]

Other:
*[[Namecoin]] - a distributed naming system based on Bitcoin technology
*[[Bitcoin Consultancy]] - an organization providing open source software and Bitcoin-related consulting
*[[Open Transactions]] - a financial crypto and digital cash software library, complementary to Bitcoin
*[[Moneychanger]] - Java-based GUI for [[Open Transactions]]

Secure Trading

2011-06-27T07:18:22Z

Da2ce7: Bold

''Secure Trading Online''

This topic is a guide on how to set up your online identity and best practices for trading with others in the Bitcoin community.

==Introduction==
Within the Bitcoin community, many are very careful with their security and identity. This is primarily for two reasons:
# There is no violent body to cover your back for you, or, more simply, there are no courts to seek assistance from if your transaction sours.
# One’s reputation is the most important thing that any user has; traders will take very little risk with new users who have not proven themselves (as they could just be last week’s scammer with a new identity).

The Bitcoin community uses a few tools to help protect privacy, and thus identity. The first and most important is a [[Securing Your Computer|Secure Computer]]. 

'''Before proceeding please make sure you have completed the [[Securing Your Computer]] guide; this guide assumes that your computer is secure both physically and in software.'''

If you are trading within Canada you are encouraged to use Interac e-transfer and Clearcoin (now closed) as outlined on [[Secure Trading-CAD-interac|this page]].

==Creating a secure identity==
The first step is to create a cryptographically secure public-private key-pair. This will be used as the basis of keeping both your wallet (see [[Securing your wallet]]) and your identity secure.

===Creating your first PGP key-pair===
A PGP key-pair serves two very important functions:
# To sign information with an unforgettable signature
# To decrypt things that other people encrypt for you

This allows you to both conduct business privately (encryption), and give out promises that you cannot deny making (signature).
==== Installing GPG ====
Virtually all Linux distributions include GPG in their default configurations. However windows doesn't provide it by default.

===== Microsoft Windows:=====
On windows, the recommend package that contains gpg is the [[Git]] package by the msysgit project. This package contains a group of unix tools that are very useful for any windows installation.

* Navigate to [[Git|msysgit]] https://code.google.com/p/msysgit/downloads/list
* Select the latest ''Git'' package. (Git-1.7.4-preview20110204.exe)
* When installing Git on the ''Adjusting your PATH environment'' screen, select: ''Run Git and included Unix tools from the Windows Command Prompt'' 
This option will install both Git and its supporting tools that include [[gpg]] into the windows PATH file. This will enable any windows application to access gpg. 
On some (rare) systems this option that replaces the default windows tools will cause issues... However on most it should be fine.
* After installation, gpg can be used by entering 'gpg' into any windows cmd shell.

==== Setting up OpenPGP email ====
Once you have GPG installed on your system, it is recommended that you use Thunderbird that works on both Windows and Linux systems:

===== All: =====
# Install Thunderbird: https://www.mozillamessaging.com/en-GB/
# Setup your email account with Thunderbird.
# Install the Enigmail plugin for Thunderbird: https://addons.mozilla.org/en-US/thunderbird/addon/enigmail/ 

Upon loading Enigmail, Thunderbird will ask you to make a new ‘identity,’ follow this wizard and you will have created your identity. 
You should backup your private key in a secure place. 
Secondary, you should create a revocation certificate and store that in a different secure place (maybe print it out and store it in your fire safe).

===Register with [#bitcoin-otc]===
Follow the guide here: http://wiki.bitcoin-otc.com/wiki/Using_bitcoin-otc

===Register the same username at the popular places:===
* [[Bitcoin Forum]]
* [[Bitcoin.it_Wiki|Bitcoin Wiki]]
* [[Bitcoin:Community_portal#IRC_Chat|Freenode IRC]]
Use a strong and different password for each of these places, keeping your passwords in a secure place. This will allow other people in the community to track you across the different Bitcoin related sites. Also making identity theft online more challenging.

==Best Practices with trading==
===Use Bitcoin-OTC===
The [[Bitcoin-otc|Bitcoin OTC]] acts as a secure 'Address Book' within the bitcoin community.
* Always require the user to become registered with #bitcoin-otc.
* Require a signed message from the fingerprint quoted at: http://bitcoin-otc.com/viewgpg.php
* Follow additional [http://wiki.bitcoin-otc.com/wiki/Using_bitcoin-otc#Risk_of_fraud recommendations] for avoiding fraud.

====Using the Web-Of-Trust====
One of the key features of the Bitcoin OTC is the Web of Trust, this allows users to 'rate' each other. One can have more confidence trading with a user that has many good ratings.
* http://bitcoin-otc.com/viewratings.php

===Make sure both parties agree to the terms of the trade with signed messages===
* Get a PGP signed quote, and check the signature.
* Send a PGP signed receipt.
This allows either party to go public if the trade has become sour and stops your trading partner from claiming the details of the agreement were somehow different. 

Search the Bitcoin Forum for the username of the person that you are trading with. Check if the user has provided constructive and useful advice to other parties. And, most importantly, check for any claims that the user has scammed.

===Use an escrow===
Trading might benefit from an escrow such that bitcoins are disbursed only after contract terms have been met. 

Two relatively new offerings are BTCrow and Eptiv.

Found in Bitcoin's community are trusted individuals willing to act as independent, third-party escrow brokers.

[[de:Sicheres_Handeln]]
[[zh-cn:交易安全]]

Secure Trading

2011-06-27T07:10:45Z

Da2ce7: /* Microsoft Windows: */ grammar

''Secure Trading Online''

This topic is a guide on how to set up your online identity and best practices for trading with others in the Bitcoin community.

==Introduction==
Within the Bitcoin community, many are very careful with their security and identity. This is primarily for two reasons:
# There is no violent body to cover your back for you, or, more simply, there are no courts to seek assistance from if your transaction sours.
# One’s reputation is the most important thing that any user has; traders will take very little risk with new users who have not proven themselves (as they could just be last week’s scammer with a new identity).

The Bitcoin community uses a few tools to help protect privacy, and thus identity. The first and most important is a [[Securing Your Computer|Secure Computer]]. 

'''Before proceeding please make sure you have completed the [[Securing Your Computer]] guide; this guide assumes that your computer is secure both physically and in software.'''

If you are trading within Canada you are encouraged to use Interac e-transfer and Clearcoin (now closed) as outlined on [[Secure Trading-CAD-interac|this page]].

==Creating a secure identity==
The first step is to create a cryptographically secure public-private key-pair. This will be used as the basis of keeping both your wallet (see [[Securing your wallet]]) and your identity secure.

===Creating your first PGP key-pair===
A PGP key-pair serves two very important functions:
# To sign information with an unforgettable signature
# To decrypt things that other people encrypt for you

This allows you to both conduct business privately (encryption), and give out promises that you cannot deny making (signature).
==== Installing GPG ====
Virtually all Linux distributions include GPG in their default configurations. However windows doesn't provide it by default.

===== Microsoft Windows:=====
On windows, the recommend package that contains gpg is the [[Git]] package by the msysgit project. This package contains a group of unix tools that are very useful for any windows installation.

* Navigate to [[Git|msysgit]] https://code.google.com/p/msysgit/downloads/list
* Select the latest 'Git' package. (Git-1.7.4-preview20110204.exe)
* When installing Git on the 'Adjusting your PATH environment' screen select 'Run Git and included Unix tools from the Windows Command Prompt' 
This option will install both Git and its supporting tools that include [[gpg]] into the windows PATH file. This will enable any windows application to access gpg. 
On some (rare) systems this option that replaces the default windows tools will cause issues... However on most it should be fine.
* After installation, gpg can be used by entering 'gpg' into any windows cmd shell.

==== Setting up OpenPGP email ====
Once you have GPG installed on your system, it is recommended that you use Thunderbird that works on both Windows and Linux systems:

===== All: =====
# Install Thunderbird: https://www.mozillamessaging.com/en-GB/
# Setup your email account with Thunderbird.
# Install the Enigmail plugin for Thunderbird: https://addons.mozilla.org/en-US/thunderbird/addon/enigmail/ 

Upon loading Enigmail, Thunderbird will ask you to make a new ‘identity,’ follow this wizard and you will have created your identity. 
You should backup your private key in a secure place. Secondary, you should create a revocation certificate and store that in a different secure place (maybe print it out and store it in your fire safe).

===Register with [#bitcoin-otc]===
Follow the guide here: http://wiki.bitcoin-otc.com/wiki/Using_bitcoin-otc

===Register the same username at the popular places:===
* [[Bitcoin Forum]]
* [[Bitcoin.it_Wiki|Bitcoin Wiki]]
* [[Bitcoin:Community_portal#IRC_Chat|Freenode IRC]]
Use a strong and different password for each of these places, keeping your passwords in a secure place. This will allow other people in the community to track you across the different Bitcoin related sites. Also making identity theft online more challenging.

==Best Practices with trading==
===Use Bitcoin-OTC===
The [[Bitcoin-otc|Bitcoin OTC]] acts as a secure 'Address Book' within the bitcoin community.
* Always require the user to become registered with #bitcoin-otc.
* Require a signed message from the fingerprint quoted at: http://bitcoin-otc.com/viewgpg.php
* Follow additional [http://wiki.bitcoin-otc.com/wiki/Using_bitcoin-otc#Risk_of_fraud recommendations] for avoiding fraud.

====Using the Web-Of-Trust====
One of the key features of the Bitcoin OTC is the Web of Trust, this allows users to 'rate' each other. One can have more confidence trading with a user that has many good ratings.
* http://bitcoin-otc.com/viewratings.php

===Make sure both parties agree to the terms of the trade with signed messages===
* Get a PGP signed quote, and check the signature.
* Send a PGP signed receipt.
This allows either party to go public if the trade has become sour and stops your trading partner from claiming the details of the agreement were somehow different. 

Search the Bitcoin Forum for the username of the person that you are trading with. Check if the user has provided constructive and useful advice to other parties. And, most importantly, check for any claims that the user has scammed.

===Use an escrow===
Trading might benefit from an escrow such that bitcoins are disbursed only after contract terms have been met. 

Two relatively new offerings are BTCrow and Eptiv.

Found in Bitcoin's community are trusted individuals willing to act as independent, third-party escrow brokers.

[[de:Sicheres_Handeln]]
[[zh-cn:交易安全]]

Secure Trading

2011-06-27T07:06:47Z

Da2ce7: Added in WOT

''Secure Trading Online''

This topic is a guide on how to set up your online identity and best practices for trading with others in the Bitcoin community.

==Introduction==
Within the Bitcoin community, many are very careful with their security and identity. This is primarily for two reasons:
# There is no violent body to cover your back for you, or, more simply, there are no courts to seek assistance from if your transaction sours.
# One’s reputation is the most important thing that any user has; traders will take very little risk with new users who have not proven themselves (as they could just be last week’s scammer with a new identity).

The Bitcoin community uses a few tools to help protect privacy, and thus identity. The first and most important is a [[Securing Your Computer|Secure Computer]]. 

'''Before proceeding please make sure you have completed the [[Securing Your Computer]] guide; this guide assumes that your computer is secure both physically and in software.'''

If you are trading within Canada you are encouraged to use Interac e-transfer and Clearcoin (now closed) as outlined on [[Secure Trading-CAD-interac|this page]].

==Creating a secure identity==
The first step is to create a cryptographically secure public-private key-pair. This will be used as the basis of keeping both your wallet (see [[Securing your wallet]]) and your identity secure.

===Creating your first PGP key-pair===
A PGP key-pair serves two very important functions:
# To sign information with an unforgettable signature
# To decrypt things that other people encrypt for you

This allows you to both conduct business privately (encryption), and give out promises that you cannot deny making (signature).
==== Installing GPG ====
Virtually all Linux distributions include GPG in their default configurations. However windows doesn't provide it by default.

===== Microsoft Windows:=====
On windows, the recommend package that contains gpg is the [[Git]] package by the msysgit project. This package contains a group of unix tools that are very useful for any windows installation.

* Navigate to [[Git|msysgit]] https://code.google.com/p/msysgit/downloads/list
* Select the latest 'Git' package. (Git-1.7.4-preview20110204.exe)
* When installing Git on the 'Adjusting your PATH environment' screen select 'Run Git and included Unix tools from the Windows Command Prompt' 
This option will install both Git and its supporting tools that include [[gpg]] into the windows PATH file. This will enable any windows application to access gpg. 
On some (rare) systems this option that replaces the default windows tools will cause issues... However on most it should be fine.
* After installation, gpg will be able to be used just by entering 'gpg' into any windows cmd shell.

==== Setting up OpenPGP email ====
Once you have GPG installed on your system, it is recommended that you use Thunderbird that works on both Windows and Linux systems:

===== All: =====
# Install Thunderbird: https://www.mozillamessaging.com/en-GB/
# Setup your email account with Thunderbird.
# Install the Enigmail plugin for Thunderbird: https://addons.mozilla.org/en-US/thunderbird/addon/enigmail/ 

Upon loading Enigmail, Thunderbird will ask you to make a new ‘identity,’ follow this wizard and you will have created your identity. 
You should backup your private key in a secure place. Secondary, you should create a revocation certificate and store that in a different secure place (maybe print it out and store it in your fire safe).

===Register with [#bitcoin-otc]===
Follow the guide here: http://wiki.bitcoin-otc.com/wiki/Using_bitcoin-otc

===Register the same username at the popular places:===
* [[Bitcoin Forum]]
* [[Bitcoin.it_Wiki|Bitcoin Wiki]]
* [[Bitcoin:Community_portal#IRC_Chat|Freenode IRC]]
Use a strong and different password for each of these places, keeping your passwords in a secure place. This will allow other people in the community to track you across the different Bitcoin related sites. Also making identity theft online more challenging.

==Best Practices with trading==
===Use Bitcoin-OTC===
The [[Bitcoin-otc|Bitcoin OTC]] acts as a secure 'Address Book' within the bitcoin community.
* Always require the user to become registered with #bitcoin-otc.
* Require a signed message from the fingerprint quoted at: http://bitcoin-otc.com/viewgpg.php
* Follow additional [http://wiki.bitcoin-otc.com/wiki/Using_bitcoin-otc#Risk_of_fraud recommendations] for avoiding fraud.

====Using the Web-Of-Trust====
One of the key features of the Bitcoin OTC is the Web of Trust, this allows users to 'rate' each other. One can have more confidence trading with a user that has many good ratings.
* http://bitcoin-otc.com/viewratings.php

===Make sure both parties agree to the terms of the trade with signed messages===
* Get a PGP signed quote, and check the signature.
* Send a PGP signed receipt.
This allows either party to go public if the trade has become sour and stops your trading partner from claiming the details of the agreement were somehow different. 

Search the Bitcoin Forum for the username of the person that you are trading with. Check if the user has provided constructive and useful advice to other parties. And, most importantly, check for any claims that the user has scammed.

===Use an escrow===
Trading might benefit from an escrow such that bitcoins are disbursed only after contract terms have been met. 

Two relatively new offerings are BTCrow and Eptiv.

Found in Bitcoin's community are trusted individuals willing to act as independent, third-party escrow brokers.

[[de:Sicheres_Handeln]]
[[zh-cn:交易安全]]

Secure Trading

2011-06-27T06:53:59Z

Da2ce7: /* Setting up OpenPGP email */

''Secure Trading Online''

This topic is a guide on how to set up your online identity and best practices for trading with others in the Bitcoin community.

==Introduction==
Within the Bitcoin community, many are very careful with their security and identity. This is primarily for two reasons:
# There is no violent body to cover your back for you, or, more simply, there are no courts to seek assistance from if your transaction sours.
# One’s reputation is the most important thing that any user has; traders will take very little risk with new users who have not proven themselves (as they could just be last week’s scammer with a new identity).

The Bitcoin community uses a few tools to help protect privacy, and thus identity. The first and most important is a [[Securing Your Computer|Secure Computer]]. 

'''Before proceeding please make sure you have completed the [[Securing Your Computer]] guide; this guide assumes that your computer is secure both physically and in software.'''

If you are trading within Canada you are encouraged to use Interac e-transfer and Clearcoin (now closed) as outlined on [[Secure Trading-CAD-interac|this page]].

==Creating a secure identity==
The first step is to create a cryptographically secure public-private key-pair. This will be used as the basis of keeping both your wallet (see [[Securing your wallet]]) and your identity secure.

===Creating your first PGP key-pair===
A PGP key-pair serves two very important functions:
# To sign information with an unforgettable signature
# To decrypt things that other people encrypt for you

This allows you to both conduct business privately (encryption), and give out promises that you cannot deny making (signature).
==== Installing GPG ====
Virtually all Linux distributions include GPG in their default configurations. However windows doesn't provide it by default.

===== Microsoft Windows:=====
On windows, the recommend package that contains gpg is the [[Git]] package by the msysgit project. This package contains a group of unix tools that are very useful for any windows installation.

* Navigate to [[Git|msysgit]] https://code.google.com/p/msysgit/downloads/list
* Select the latest 'Git' package. (Git-1.7.4-preview20110204.exe)
* When installing Git on the 'Adjusting your PATH environment' screen select 'Run Git and included Unix tools from the Windows Command Prompt' 
This option will install both Git and its supporting tools that include [[gpg]] into the windows PATH file. This will enable any windows application to access gpg. 
On some (rare) systems this option that replaces the default windows tools will cause issues... However on most it should be fine.
* After installation, gpg will be able to be used just by entering 'gpg' into any windows cmd shell.

==== Setting up OpenPGP email ====
Once you have GPG installed on your system, it is recommended that you use Thunderbird that works on both Windows and Linux systems:

===== All: =====
# Install Thunderbird: https://www.mozillamessaging.com/en-GB/
# Setup your email account with Thunderbird.
# Install the Enigmail plugin for Thunderbird: https://addons.mozilla.org/en-US/thunderbird/addon/enigmail/ 

Upon loading Enigmail, Thunderbird will ask you to make a new ‘identity,’ follow this wizard and you will have created your identity. 
You should backup your private key in a secure place. Secondary, you should create a revocation certificate and store that in a different secure place (maybe print it out and store it in your fire safe).

===Register with [#bitcoin-otc]===
Follow the guide here: http://wiki.bitcoin-otc.com/wiki/Using_bitcoin-otc

===Register the same username at the popular places:===
* [[Bitcoin Forum]]
* [[Bitcoin.it_Wiki|Bitcoin Wiki]]
* [[Bitcoin:Community_portal#IRC_Chat|Freenode IRC]]
Use a strong and different password for each of these places, keeping your passwords in a secure place. This will allow other people in the community to track you across the different Bitcoin related sites. Also making identity theft online more challenging.

==Best Practices with trading==
===Use Bitcoin-OTC===
* Always require the user to become registered with #bitcoin-otc.
* Require a signed message from the fingerprint quoted at: http://bitcoin-otc.com/viewgpg.php
* Follow additional [http://wiki.bitcoin-otc.com/wiki/Using_bitcoin-otc#Risk_of_fraud recommendations] for avoiding fraud.

===Make sure both parties agree to the terms of the trade with signed messages===
* Get a PGP signed quote, and check the signature.
* Send a PGP signed receipt.
This allows either party to go public if the trade has become sour and stops your trading partner from claiming the details of the agreement were somehow different. 

Search the Bitcoin Forum for the username of the person that you are trading with. Check if the user has provided constructive and useful advice to other parties. And, most importantly, check for any claims that the user has scammed.

===Use an escrow===
Trading might benefit from an escrow such that bitcoins are disbursed only after contract terms have been met. 

Two relatively new offerings are BTCrow and Eptiv.

Found in Bitcoin's community are trusted individuals willing to act as independent, third-party escrow brokers.

[[de:Sicheres_Handeln]]
[[zh-cn:交易安全]]

Secure Trading

2011-06-27T06:47:02Z

Da2ce7: clearcoin closed

''Secure Trading Online''

This topic is a guide on how to set up your online identity and best practices for trading with others in the Bitcoin community.

==Introduction==
Within the Bitcoin community, many are very careful with their security and identity. This is primarily for two reasons:
# There is no violent body to cover your back for you, or, more simply, there are no courts to seek assistance from if your transaction sours.
# One’s reputation is the most important thing that any user has; traders will take very little risk with new users who have not proven themselves (as they could just be last week’s scammer with a new identity).

The Bitcoin community uses a few tools to help protect privacy, and thus identity. The first and most important is a [[Securing Your Computer|Secure Computer]]. 

'''Before proceeding please make sure you have completed the [[Securing Your Computer]] guide; this guide assumes that your computer is secure both physically and in software.'''

If you are trading within Canada you are encouraged to use Interac e-transfer and Clearcoin (now closed) as outlined on [[Secure Trading-CAD-interac|this page]].

==Creating a secure identity==
The first step is to create a cryptographically secure public-private key-pair. This will be used as the basis of keeping both your wallet (see [[Securing your wallet]]) and your identity secure.

===Creating your first PGP key-pair===
A PGP key-pair serves two very important functions:
# To sign information with an unforgettable signature
# To decrypt things that other people encrypt for you

This allows you to both conduct business privately (encryption), and give out promises that you cannot deny making (signature).
==== Installing GPG ====
Virtually all Linux distributions include GPG in their default configurations. However windows doesn't provide it by default.

===== Microsoft Windows:=====
On windows, the recommend package that contains gpg is the [[Git]] package by the msysgit project. This package contains a group of unix tools that are very useful for any windows installation.

* Navigate to [[Git|msysgit]] https://code.google.com/p/msysgit/downloads/list
* Select the latest 'Git' package. (Git-1.7.4-preview20110204.exe)
* When installing Git on the 'Adjusting your PATH environment' screen select 'Run Git and included Unix tools from the Windows Command Prompt' 
This option will install both Git and its supporting tools that include [[gpg]] into the windows PATH file. This will enable any windows application to access gpg. 
On some (rare) systems this option that replaces the default windows tools will cause issues... However on most it should be fine.
* After installation, gpg will be able to be used just by entering 'gpg' into any windows cmd shell.

==== Setting up OpenPGP email ====
Once you have GPG installed on your system, it is recommended that you use Thunderbird (that works on both Windows and Linux systems:

===== All: =====
# Install Thunderbird: https://www.mozillamessaging.com/en-GB/
# Setup your email account with Thunderbird.
# Install the Enigmail plugin for Thunderbird: https://addons.mozilla.org/en-US/thunderbird/addon/enigmail/ 

Upon loading Enigmail, Thunderbird will ask you to make a new ‘identity,’ follow this wizard and you will have created your identity. 
You should backup your private key in a secure place. Secondary, you should create a revocation certificate and store that in a different secure place (maybe print it out and store it in your fire safe).

===Register with [#bitcoin-otc]===
Follow the guide here: http://wiki.bitcoin-otc.com/wiki/Using_bitcoin-otc

===Register the same username at the popular places:===
* [[Bitcoin Forum]]
* [[Bitcoin.it_Wiki|Bitcoin Wiki]]
* [[Bitcoin:Community_portal#IRC_Chat|Freenode IRC]]
Use a strong and different password for each of these places, keeping your passwords in a secure place. This will allow other people in the community to track you across the different Bitcoin related sites. Also making identity theft online more challenging.

==Best Practices with trading==
===Use Bitcoin-OTC===
* Always require the user to become registered with #bitcoin-otc.
* Require a signed message from the fingerprint quoted at: http://bitcoin-otc.com/viewgpg.php
* Follow additional [http://wiki.bitcoin-otc.com/wiki/Using_bitcoin-otc#Risk_of_fraud recommendations] for avoiding fraud.

===Make sure both parties agree to the terms of the trade with signed messages===
* Get a PGP signed quote, and check the signature.
* Send a PGP signed receipt.
This allows either party to go public if the trade has become sour and stops your trading partner from claiming the details of the agreement were somehow different. 

Search the Bitcoin Forum for the username of the person that you are trading with. Check if the user has provided constructive and useful advice to other parties. And, most importantly, check for any claims that the user has scammed.

===Use an escrow===
Trading might benefit from an escrow such that bitcoins are disbursed only after contract terms have been met. 

Two relatively new offerings are BTCrow and Eptiv.

Found in Bitcoin's community are trusted individuals willing to act as independent, third-party escrow brokers.

[[de:Sicheres_Handeln]]
[[zh-cn:交易安全]]

Secure Trading

2011-06-27T06:31:33Z

Da2ce7:

''Secure Trading Online''

This topic is a guide on how to set up your online identity and best practices for trading with others in the Bitcoin community.

==Introduction==
Within the Bitcoin community, many are very careful with their security and identity. This is primarily for two reasons:
# There is no violent body to cover your back for you, or, more simply, there are no courts to seek assistance from if your transaction sours.
# One’s reputation is the most important thing that any user has; traders will take very little risk with new users who have not proven themselves (as they could just be last week’s scammer with a new identity).

The Bitcoin community uses a few tools to help protect privacy, and thus identity. The first and most important is a [[Securing Your Computer|Secure Computer]]. 

'''Before proceeding please make sure you have completed the [[Securing Your Computer]] guide; this guide assumes that your computer is secure both physically and in software.'''

If you are trading within Canada you are encouraged to use Interac e-transfer and Clearcoin as outlined on [[Secure Trading-CAD-interac|this page]].

==Creating a secure identity==
The first step is to create a cryptographically secure public-private key-pair. This will be used as the basis of keeping both your wallet (see [[Securing your wallet]]) and your identity secure.

===Creating your first PGP key-pair===
A PGP key-pair serves two very important functions:
# To sign information with an unforgettable signature
# To decrypt things that other people encrypt for you

This allows you to both conduct business privately (encryption), and give out promises that you cannot deny making (signature).
==== Installing GPG ====
Virtually all Linux distributions include GPG in their default configurations. However windows doesn't provide it by default.

===== Microsoft Windows:=====
On windows, the recommend package that contains gpg is the [[Git]] package by the msysgit project. This package contains a group of unix tools that are very useful for any windows installation.

* Navigate to [[Git|msysgit]] https://code.google.com/p/msysgit/downloads/list
* Select the latest 'Git' package. (Git-1.7.4-preview20110204.exe)
* When installing Git on the 'Adjusting your PATH environment' screen select 'Run Git and included Unix tools from the Windows Command Prompt' 
This option will install both Git and its supporting tools that include [[gpg]] into the windows PATH file. This will enable any windows application to access gpg. 
On some (rare) systems this option that replaces the default windows tools will cause issues... However on most it should be fine.
* After installation, gpg will be able to be used just by entering 'gpg' into any windows cmd shell.

==== Setting up OpenPGP email ====
Once you have GPG installed on your system, it is recommended that you use Thunderbird (that works on both Windows and Linux systems:

===== All: =====
# Install Thunderbird: https://www.mozillamessaging.com/en-GB/
# Setup your email account with Thunderbird.
# Install the Enigmail plugin for Thunderbird: https://addons.mozilla.org/en-US/thunderbird/addon/enigmail/ 

Upon loading Enigmail, Thunderbird will ask you to make a new ‘identity,’ follow this wizard and you will have created your identity. 
You should backup your private key in a secure place. Secondary, you should create a revocation certificate and store that in a different secure place (maybe print it out and store it in your fire safe).

===Register with [#bitcoin-otc]===
Follow the guide here: http://wiki.bitcoin-otc.com/wiki/Using_bitcoin-otc

===Register the same username at the popular places:===
* [[Bitcoin Forum]]
* [[Bitcoin.it_Wiki|Bitcoin Wiki]]
* [[Bitcoin:Community_portal#IRC_Chat|Freenode IRC]]
Use a strong and different password for each of these places, keeping your passwords in a secure place. This will allow other people in the community to track you across the different Bitcoin related sites. Also making identity theft online more challenging.

==Best Practices with trading==
===Use Bitcoin-OTC===
* Always require the user to become registered with #bitcoin-otc.
* Require a signed message from the fingerprint quoted at: http://bitcoin-otc.com/viewgpg.php
* Follow additional [http://wiki.bitcoin-otc.com/wiki/Using_bitcoin-otc#Risk_of_fraud recommendations] for avoiding fraud.

===Make sure both parties agree to the terms of the trade with signed messages===
* Get a PGP signed quote, and check the signature.
* Send a PGP signed receipt.
This allows either party to go public if the trade has become sour and stops your trading partner from claiming the details of the agreement were somehow different. 

Search the Bitcoin Forum for the username of the person that you are trading with. Check if the user has provided constructive and useful advice to other parties. And, most importantly, check for any claims that the user has scammed.

===Use an escrow===
Trading might benefit from an escrow such that bitcoins are disbursed only after contract terms have been met. 

Two relatively new offerings are BTCrow and Eptiv.

Found in Bitcoin's community are trusted individuals willing to act as independent, third-party escrow brokers.

[[de:Sicheres_Handeln]]
[[zh-cn:交易安全]]

Secure Trading

2011-06-27T06:30:09Z

Da2ce7: /* Microsoft Windows: */ spelling

''Secure Trading Online''

This topic is a guide on how to set up your online identity and best practices for trading with others in the Bitcoin community.

==Introduction==
Within the Bitcoin community, many are very careful with their security and identity. This is primarily for two reasons:
# There is no violent body to cover your back for you, or, more simply, there are no courts to seek assistance from if your transaction sours.
# One’s reputation is the most important thing that any user has; traders will take very little risk with new users who have not proven themselves (as they could just be last week’s scammer with a new identity).

The Bitcoin community uses a few tools to help protect privacy, and thus identity. The first and most important is a [[Securing Your Computer|Secure Computer]]. 

'''Before proceeding please make sure you have completed the [[Securing Your Computer]] guide; this guide assumes that your computer is secure both physically and in software.'''

If you are trading within Canada you are encouraged to use Interac e-transfer and Clearcoin as outlined on [[Secure Trading-CAD-interac|this page]].

==Creating a secure identity==
The first step is to create a cryptographically secure public-private key-pair. This will be used as the basis of keeping both your wallet (see [[Securing your wallet]]) and your identity secure.

===Creating your first PGP key-pair===
A PGP key-pair serves two very important functions:
# To sign information with an unforgettable signature
# To decrypt things that other people encrypt for you

This allows you to both conduct business privately (encryption), and give out promises that you cannot deny making (signature).
==== Installing GPG ====
Virtually all Linux distributions include GPG in their default configurations. However windows doesn't provide it by default.

===== Microsoft Windows:=====
On windows, the recommend package that contains gpg is the 'Git' package by the msysgit project. This package contains a group of unix tools that are very useful for any windows installation.

* Navigate to [msysgit] https://code.google.com/p/msysgit/downloads/list
* Select the latest 'Git' package. (Git-1.7.4-preview20110204.exe)
* When installing Git on the 'Adjusting your PATH environment' screen select 'Run Git and included Unix tools from the Windows Command Prompt' 
This option will install both Git and its supporting tools that include [gpg] into the windows PATH file. This will enable any windows application to access gpg. 
On some (rare) systems this option that replaces the default windows tools will cause issues... However on most it should be fine.
* After installation, gpg will be able to be used just by entering 'gpg' into any windows cmd shell.

==== Setting up OpenPGP email ====
Once you have GPG installed on your system, it is recommended that you use Thunderbird (that works on both Windows and Linux systems:

===== All: =====
# Install Thunderbird: https://www.mozillamessaging.com/en-GB/
# Setup your email account with Thunderbird.
# Install the Enigmail plugin for Thunderbird: https://addons.mozilla.org/en-US/thunderbird/addon/enigmail/ 

Upon loading Enigmail, Thunderbird will ask you to make a new ‘identity,’ follow this wizard and you will have created your identity. 
You should backup your private key in a secure place. Secondary, you should create a revocation certificate and store that in a different secure place (maybe print it out and store it in your fire safe).

===Register with [#bitcoin-otc]===
Follow the guide here: http://wiki.bitcoin-otc.com/wiki/Using_bitcoin-otc

===Register the same username at the popular places:===
* [[Bitcoin Forum]]
* [[Bitcoin.it_Wiki|Bitcoin Wiki]]
* [[Bitcoin:Community_portal#IRC_Chat|Freenode IRC]]
Use a strong and different password for each of these places, keeping your passwords in a secure place. This will allow other people in the community to track you across the different Bitcoin related sites. Also making identity theft online more challenging.

==Best Practices with trading==
===Use Bitcoin-OTC===
* Always require the user to become registered with #bitcoin-otc.
* Require a signed message from the fingerprint quoted at: http://bitcoin-otc.com/viewgpg.php
* Follow additional [http://wiki.bitcoin-otc.com/wiki/Using_bitcoin-otc#Risk_of_fraud recommendations] for avoiding fraud.

===Make sure both parties agree to the terms of the trade with signed messages===
* Get a PGP signed quote, and check the signature.
* Send a PGP signed receipt.
This allows either party to go public if the trade has become sour and stops your trading partner from claiming the details of the agreement were somehow different. 

Search the Bitcoin Forum for the username of the person that you are trading with. Check if the user has provided constructive and useful advice to other parties. And, most importantly, check for any claims that the user has scammed.

===Use an escrow===
Trading might benefit from an escrow such that bitcoins are disbursed only after contract terms have been met. 

Two relatively new offerings are BTCrow and Eptiv.

Found in Bitcoin's community are trusted individuals willing to act as independent, third-party escrow brokers.

[[de:Sicheres_Handeln]]
[[zh-cn:交易安全]]

Secure Trading

2011-06-27T06:29:44Z

Da2ce7: Change from GPG4Win to msysgit Git, a far better choice for windows.

''Secure Trading Online''

This topic is a guide on how to set up your online identity and best practices for trading with others in the Bitcoin community.

==Introduction==
Within the Bitcoin community, many are very careful with their security and identity. This is primarily for two reasons:
# There is no violent body to cover your back for you, or, more simply, there are no courts to seek assistance from if your transaction sours.
# One’s reputation is the most important thing that any user has; traders will take very little risk with new users who have not proven themselves (as they could just be last week’s scammer with a new identity).

The Bitcoin community uses a few tools to help protect privacy, and thus identity. The first and most important is a [[Securing Your Computer|Secure Computer]]. 

'''Before proceeding please make sure you have completed the [[Securing Your Computer]] guide; this guide assumes that your computer is secure both physically and in software.'''

If you are trading within Canada you are encouraged to use Interac e-transfer and Clearcoin as outlined on [[Secure Trading-CAD-interac|this page]].

==Creating a secure identity==
The first step is to create a cryptographically secure public-private key-pair. This will be used as the basis of keeping both your wallet (see [[Securing your wallet]]) and your identity secure.

===Creating your first PGP key-pair===
A PGP key-pair serves two very important functions:
# To sign information with an unforgettable signature
# To decrypt things that other people encrypt for you

This allows you to both conduct business privately (encryption), and give out promises that you cannot deny making (signature).
==== Installing GPG ====
Virtually all Linux distributions include GPG in their default configurations. However windows doesn't provide it by default.

===== Microsoft Windows:=====
On windows, the recommend package that contains gpg is the 'Git' package by the msysgit project. This package contains a group of unix tools that are very useful for any windows installation.

* Got to [msysgit] https://code.google.com/p/msysgit/downloads/list
* Select the latest 'Git' package. (Git-1.7.4-preview20110204.exe)
* When installing Git on the 'Adjusting your PATH environment' screen select 'Run Git and included Unix tools from the Windows Command Prompt' 
This option will install both Git and its supporting tools that include [gpg] into the windows PATH file. This will enable any windows application to access gpg. 
On some (rare) systems this option that replaces the default windows tools will cause issues... However on most it should be fine.
* After installation, gpg will be able to be used just by entering 'gpg' into any windows cmd shell.

==== Setting up OpenPGP email ====
Once you have GPG installed on your system, it is recommended that you use Thunderbird (that works on both Windows and Linux systems:

===== All: =====
# Install Thunderbird: https://www.mozillamessaging.com/en-GB/
# Setup your email account with Thunderbird.
# Install the Enigmail plugin for Thunderbird: https://addons.mozilla.org/en-US/thunderbird/addon/enigmail/ 

Upon loading Enigmail, Thunderbird will ask you to make a new ‘identity,’ follow this wizard and you will have created your identity. 
You should backup your private key in a secure place. Secondary, you should create a revocation certificate and store that in a different secure place (maybe print it out and store it in your fire safe).

===Register with [#bitcoin-otc]===
Follow the guide here: http://wiki.bitcoin-otc.com/wiki/Using_bitcoin-otc

===Register the same username at the popular places:===
* [[Bitcoin Forum]]
* [[Bitcoin.it_Wiki|Bitcoin Wiki]]
* [[Bitcoin:Community_portal#IRC_Chat|Freenode IRC]]
Use a strong and different password for each of these places, keeping your passwords in a secure place. This will allow other people in the community to track you across the different Bitcoin related sites. Also making identity theft online more challenging.

==Best Practices with trading==
===Use Bitcoin-OTC===
* Always require the user to become registered with #bitcoin-otc.
* Require a signed message from the fingerprint quoted at: http://bitcoin-otc.com/viewgpg.php
* Follow additional [http://wiki.bitcoin-otc.com/wiki/Using_bitcoin-otc#Risk_of_fraud recommendations] for avoiding fraud.

===Make sure both parties agree to the terms of the trade with signed messages===
* Get a PGP signed quote, and check the signature.
* Send a PGP signed receipt.
This allows either party to go public if the trade has become sour and stops your trading partner from claiming the details of the agreement were somehow different. 

Search the Bitcoin Forum for the username of the person that you are trading with. Check if the user has provided constructive and useful advice to other parties. And, most importantly, check for any claims that the user has scammed.

===Use an escrow===
Trading might benefit from an escrow such that bitcoins are disbursed only after contract terms have been met. 

Two relatively new offerings are BTCrow and Eptiv.

Found in Bitcoin's community are trusted individuals willing to act as independent, third-party escrow brokers.

[[de:Sicheres_Handeln]]
[[zh-cn:交易安全]]

IRC channels

2011-06-12T14:41:45Z

Da2ce7: Added #bitcoin-gaming

Most of the following Bitcoin-related IRC channels are available on [http://www.freenode.net Freenode]:

==Bitcoin Project==
{| class="wikitable"
! Channel !! Description
|-
| {{Freenode IRC|bitcoin}} || General Bitcoin-related discussion.
|-
| {{Freenode IRC|bitcoin-otc|text=[[bitcoin-otc|#bitcoin-otc]]}} || Over-the-counter trading marketplace and discussion.
|-
| {{Freenode IRC|bitcoin-otc-ticker|bitcoin-otc-ticker}} || Streaming market data form the [[#bitcoin-otc]] order book.
|-
| {{Freenode IRC|bitcoin-pit}} || Only over-the-counter trading.
|-
| {{Freenode IRC|bitcoin-auction}} || Live auctions over IRC.
|-
| {{Freenode IRC|bitcoin-market}} || Streaming market data (only), no chat.
|-
| {{Freenode IRC|bitcoin-watch|text=[[Bitcoin-Watch|#bitcoin-watch]]}} || Streaming Bitcoin transactions, including market data.
|-
| {{Freenode IRC|bitcoin-dev}} || Bitcoin software development.
|-
| {{Freenode IRC|bitcoin-mining}} || Discussion and support related to mining.
|-
| {{Freenode IRC|bitcoin-politics}} || Discuss politics with other Bitcoin users.
|-
| {{Freenode IRC|bitcoin-gaming}} || Bitcoin gamers hangout.
|-
| {{Freenode IRC|bc-news}} || RSS News related to Bitcoin.
|-
| {{Freenode IRC|bitcoin-marketing}} || Marketing and promotion of bitcoin
|-
| {{Freenode IRC|bitcoin-gentoo}} || Gentoo community.
|}

===Local communities===

{| class="wikitable"
! Channel !! Description
|-
| {{Freenode IRC|bitcoin-otc-eu}} || European OTC trading marketplace.
|-
| {{Freenode IRC|bitcoin-otc-ru}} || Russian OTC trading marketplace.
|-
| {{Freenode IRC|bitcoin-aus}} || Aussie bitcoin community.
|-
| {{Freenode IRC|bitcoin-br}} || Brazilian bitcoin community.
|-
| {{Freenode IRC|bitcoin-cad}} || Canadian bitcoin community.
|-
| {{Freenode IRC|bitcoin-cn}} || Chinese bitcoin community.
|-
| {{Freenode IRC|bitcoin-de}} || German bitcoin community.
|-
| {{Freenode IRC|bitcoin-dk}} || Danish bitcoin community.
|-
| {{Freenode IRC|bitcoin-nederland}} || Dutch bitcoin community.
|-
| {{Freenode IRC|bitcoin-es}} || Spanish-speaking bitcoin community.
|-
| {{Freenode IRC|bitcoin-fr}} || French bitcoin community.
|-
| {{Freenode IRC|bitcoin-it}} || Italian bitcoin community.
|}

==Related Communities==

{| class="wikitable"
! Channel !! Description
|-
| {{Freenode IRC|eligius}} || [[Eligius]] pool community
|-
| {{Freenode IRC|namecoin}} || [[Namecoin]] and the [[Dot-bit]] project.
|-
| {{Freenode IRC|witcoin}} || [[Witcoin]] social news and user generated content.
|-
| [irc://irc.foonetic.net/xkcd-bitcoin IRC] [http://irc.lc/foonetic/xkcd-bitcoin/Miner@@@ Web] #xkcd-bitcoin || [https://en.bitcoin.it/wiki/XKCD_Pool XKCD Pool]
|-
| [irc://irc.quakenet.org/bitcoins.lc IRC] [http://irc.lc/quakenet/bitcoins.lc/Miner@@@ Web] #bitcoins.lc @ Quakenet || [http://www.bitcoins.lc Bitcoins.lc Pool]
|}

Gribble

2011-06-12T13:58:04Z

Da2ce7: /* list of commands */

[http://gribble.sourceforge.net/ gribble] is a modified Supybot IRC bot, carrying some useful bitcoin-related commands and factoids. The bot's command sequence is ';;', to issue any command just start a line with two semicolons. You can also issue inline commands with two commas.

It is present on #bitcoin-dev (bitcoin information queries), #bitcoin-market (real time streaming quotes from bitcoinmarket.com and mtgox.com), #bitcoin-otc (facilitate over-the-counter trading, with the OTC order book and OTC web of trust). You can also PM commands to gribble and it will PM back.

==General Info==

To get help on any command, try 'help <command>', to get a list of bitcoin-related commands, run 'apropos bc', and to get a list of factoids, run command 'facts', and click on the link supplied.

==List of commands==

===Mining/network/hashrate stats===

* '''bc,blocks''' - show the current number of blocks in the bitcoin block chain
* '''bc,calc''' - given a hash rate in Khps, calculate the expected average time to generate a block, at current difficulty. For example, to see the average time for 1000 Khps, run 'bc,calc 1000'.
* '''bc,calcd''' - given a hash rate in Khps, and a difficulty level, calculate the expected average time to generate a block at that difficulty. For example, to see the average time for 1000 Khps at difficulty 1, run 'bc,calc 1000 1'.
* '''bc,diff''' - show the current generation difficulty
* '''bc,diffchange''' - show estimated percent change in difficulty
* '''bc,estimate''' - show the estimate of the next difficulty<ref>[http://www.bitcoin.org/smf/index.php?topic=3247.0 Estimate is usually wildly inaccurate for 100-200 blocks after a difficulty change due to insufficient sample size.]</ref>
* '''bc,gen''' - given the hash rate in Khps, calculate expected BTC generation per day and per hour, at current difficulty.
* '''bc,gend''' - given the hash rate in Khps, and a difficulty level, calculate expected BTC generation per day and per hour at that difficulty.
* '''bc,hextarget''' - show the current difficulty target in hex.
* '''bc,nethash''' - current 3-day estimate of network hash power, in Ghps.
* '''bc,nexttarget''' - show the block at which the next difficulty change will take place
* '''bc,interval''' - show the average time between blocks, over the past 1000 blocks. If given optional integer argument, use that many blocks for the estimate.
* '''bc,prob''' - show the probability of getting at least one block at given Khps, in a given time period. E.g., to see probability of getting a block at 1000 Khps, in 2 years and 1 week, try 'bc,prob 1000 2y 1w'. Time takes input in years, weeks, days, hours, minutes, and seconds.
* '''bc,probd''' - show the probability of getting at least one block at given Khps, given difficulty, in a given time period. Same as '''bc,prob''' but supply a difficulty after the hash rate. E.g., 'bc,probd 10000000 600000 1w 2d'
* '''bc,spotestimate''' - current 3-day estimate of network power, in terms of difficulty.
* '''bc,stats''' - show some statistics about the block chain - number of blocks, difficulty, estimated next difficulty target, time to next difficulty
* '''bc,timetonext''' - show estimated time to reach the next difficulty target
* '''bc,totalbc''' - show total number of bitcoins in existence.

Big kudos goes out to theymos for providing a web interface to [http://blockexplorer.com/q/ real time statistics about the bitcoin block chain].

===Markets and exchange rates===

* '''bc,bcm''' - show the market snapshot from bitcoinmarket.com
* '''bc,mtgox''' - show the market snapshot for mtgox.com
* '''bc,avgprc''' - show average 24h, 7d, and 30d trading prices of BTC in various currencies.
* '''bc,24hprc''' - show average 24h price of BTC in USD.
* '''bc,convert''' - convert bitcoin price, based on MtGox last, to currency you specify. e.g., try 'bc,convert eur' for euros.
* '''bc,fx''' - show various currency exchange rates
* '''bc,xau''' - show price of gold in BTC
* '''ticker''' - show pretty-printed mtgox ticker. Takes optional argument of '--bid', '--ask', '--last', '--high', or '--low', to show just that numeric value (useful for command nesting in calculations)
* '''bids''' - given a numeric argument, shows how many total btc are being demanded on MtGox at or over the given price. If optional '--under' argument given, looks under the price.
* '''asks''' - given a numeric argument, shows how many total btc are being offered on MtGox at or below given price. If optional '--over' argument given, looks over the price.

===Mining pool statistics===

* '''bc,slushpool''' - show the mining hash rate of the [http://mining.bitcoin.cz slush mining pool], in Khps.
* '''bc,eligius''' - show the mining hash rate of the Eligius mining pool, in Khps
* '''bc,swepool''' - show the mining hash rate of the Swepool mining pool, in Khps
* '''bc,btcguild''' - show the mining hash rate of the Btcguild mining pool, in Khps
* '''bc,deepbit''' - show the mining hash rate of the Deepbit mining pool, in Khps

===Other===

* '''bc,help''' - show list of 'bc,' commands - same as 'apropos bc'.
* '''bc,wiki''' - fetch a link to a page in this wiki, based on a search string. For example, to see a link to this page, try 'bc,wiki gribble'.

===bitcoin-otc related info===

* See [http://wiki.bitcoin-otc.com/wiki/Using_bitcoin-otc OTC guide] about using the order book
* See [http://wiki.bitcoin-otc.com/wiki/GPG_authentication OTC GPG guide] about using the gpg authentication system
* See [http://wiki.bitcoin-otc.com/wiki/OTC_Rating_System Web of Trust guide] about using the rating system/web of trust

===General commands===

The above list is specifically for bitcoin-related commands. See [http://sourceforge.net/apps/mediawiki/gribble/index.php?title=Using_Gribble_on_Sourceforge this page] for list and help of most commonly used non-bitcoin-related gribble commands. You can find more helpful info on the [http://gribble.sourceforge.net/ gribble] project page, or by exploring the bot with 'list' and 'help' commands.

==References==
<references />

==Factoids==

* [http://gribble.dreamhosters.com/viewfactoids.php?db=%23bitcoin-dev factoids for #bitcoin-dev channel]
* [http://gribble.dreamhosters.com/viewfactoids.php?db=%23bitcoin-otc factoids for #bitcoin-otc channel]

==Examples==

<me> ;;bc,blocks
<gribble> 96009

<me> Check out the current difficulty! ,,bc,diff
<gribble> 8078.19525793

<me> Here is a list of all gribble bitcoin commands: ,,(apropos bc)
<gribble> Alias bc,bcm, Alias bc,blocks, Alias bc,btcex, Alias bc,calc, Alias bc,diff, Alias bc,estimate, Alias bc,mtgox, Alias bc,nexttarget, Alias bc,stats, Alias bc,timetonext, and Alias bc,totalbc

<me> ;;list
<gribble> Admin, Alias, Anonymous, [...]

<me> ;;list Alias
<gribble> ?, about, add, bc,bcm [...], sfwikisearch, sl, slap, smack, [...]

<me> ;;sl bitcoin
<gribble> http://www.bitcoin.org/ | Bitcoin is a peer-to-peer digital currency. Peer-to-peer (P2P) means [...]

<me> Some commands have more than one argument. Surround with parens.
<me> e.g., Is your wallet safe? ,,(bc,wiki secure wallet)
<gribble> https://en.bitcoin.it/wiki/Securing_your_wallet | Apr 6, 2011 ... However a few [...]

<me> ;;calc 25 USD in EUR
<gribble> 25 US dollars = 17.2248 euros

===list of commands===

?, about, action, add, alert, alias, announce, announce add, announce list, announce remove, any, aol, apply, apropos, asks, at, auth, author, azn, ban add 
ban list, ban remove, base, bashorg, bc,24hprc, bc,avgprc, bc,bcm, bc,blocks, bc,btceur, bc,btcgbp, bc,btcguild, bc,btcrub, bc,calc, bc,calcd, bc,channels, bc,convert, bc,deepbit, bc,diff, bc,diffchange, bc,eligius, bc,estimate, bc,fx, bc,gen, bc,gend, bc,help, bc,hextarget, bc,interval, bc,mtgox, bc,mtgoxask, bc,mtgoxbid, bc,mtgoxlast, bc,nethash, bc,nexttarget, bc,price, bc,prob, bc,probd, bc,slushpool, bc,spotestimate, bc,stats, bc,swepool, bc,timetonext, bc,totalbc, bc,wiki, bc,xau, bids, binary, blockmonitor, bold, book, bot, botsnack, boturl, botweb, buy 
cache, calc, call, cand, capabilities, capability add, capability list, capability remove, capability set, capability setdefault, capability unset, capitalize, ceq, change, changekey, changename, channel, channeldb, channels, channelstats, check, cheer, chr, cif, clearq, cmd, coin, collect, color, colorize, command, commands, concat, config, configure, connect, contributors, convert, cor, countargs, cpu, crypt, ctell, ctime, cut, cxor, cycle 
decode, default, defaultcapability, defaultplugin, dehalfop, deleteuser, deop, devoice, dice, dict, dictionaries, direct, disable, disconnect, dns, do, doctype, driver 
eauth, ebay, echo, ed, eightball, elapsed, enable, encode, environ, eregister, errno, eval, everify, exec, exn, export 
factlist, facts, feed, fetch, field, fight, fit, flush, forget, format, fortune 
ge, get, getprefix, getrating, gettrust, ghost, give, giveme, giveout, gnu, google, gribble, gt 
h, halfop, headers, hebrew, help, hexip, hexlify, histsearch, hostmask, hostmask add, hostmask list, hostmask remove, hug 
icalc, ident, identify, ignore, ignore add, ignore list, ignore remove, info, insert, invite, ircquote, isitdown 
jeffk, join 
kban, key, kick 
last, latency, le, learn, leet, len, levenshtein, limit, list, lithp, load, lobotomy add, lobotomy list, lobotomy remove, lock, logmark, lower, ls, lt, lucky 
match, md5, mode, moderate, monologue, more, morse, mp 
names, nceq, ne, net, netcraft, networks, nge, ngt, nick, nicks, nle, nlt, nne, notes, notice 
oobhresponse, op, ord, otc, outfilter 
part, password, pet, petuser, pgp, phonebook, pid, ping, plugin, plugins, pong, private, processes, progstats 
quit 
rainbow, random, rank, rate, rated, re, reconnect, redo, refresh, register, reload, remove, rename, reorder, repeat, replace, replies, reply, repr, restore, reverse, rot13, roulette, rpn, rss 
sample, say, scramble, search, seconds, seen, sell, sendquote, separator, server, set, set password, set secure, settrace, sfideasearch, sflaconica, sfticketsearch, sfuserpage, sfwikisearch, sha, show, shrink, shuffle, simpleeval, since, size, sl, slap, slogan, smack, soundex, source, spell, spellit, squish, start, stats, status, stop, stripcolor, success, sudo, suicide, supa1337, swap, synonym 
targetproject, tell, texthelp, threads, ticker, time, title, tn,blocks, tn,diff, topic, translate, trustinfo 
ud, unauth, unban, unbinary, underline, undo, undup, unhexlify, unidentify, units, uniud, unload, unlock, unmoderate, unmorse, unrate, unregister, unrename, unsettrace, until, upkeep, upper, uptime, urlquote, urlunquote, user, username 
vacuum, verify, version, view, voice 
whatis, whoami, whois, wk, wp, wtf 
xor 
yt

Gribble

2011-06-12T13:57:42Z

Da2ce7: List of gribble commands

[http://gribble.sourceforge.net/ gribble] is a modified Supybot IRC bot, carrying some useful bitcoin-related commands and factoids. The bot's command sequence is ';;', to issue any command just start a line with two semicolons. You can also issue inline commands with two commas.

It is present on #bitcoin-dev (bitcoin information queries), #bitcoin-market (real time streaming quotes from bitcoinmarket.com and mtgox.com), #bitcoin-otc (facilitate over-the-counter trading, with the OTC order book and OTC web of trust). You can also PM commands to gribble and it will PM back.

==General Info==

To get help on any command, try 'help <command>', to get a list of bitcoin-related commands, run 'apropos bc', and to get a list of factoids, run command 'facts', and click on the link supplied.

==List of commands==

===Mining/network/hashrate stats===

* '''bc,blocks''' - show the current number of blocks in the bitcoin block chain
* '''bc,calc''' - given a hash rate in Khps, calculate the expected average time to generate a block, at current difficulty. For example, to see the average time for 1000 Khps, run 'bc,calc 1000'.
* '''bc,calcd''' - given a hash rate in Khps, and a difficulty level, calculate the expected average time to generate a block at that difficulty. For example, to see the average time for 1000 Khps at difficulty 1, run 'bc,calc 1000 1'.
* '''bc,diff''' - show the current generation difficulty
* '''bc,diffchange''' - show estimated percent change in difficulty
* '''bc,estimate''' - show the estimate of the next difficulty<ref>[http://www.bitcoin.org/smf/index.php?topic=3247.0 Estimate is usually wildly inaccurate for 100-200 blocks after a difficulty change due to insufficient sample size.]</ref>
* '''bc,gen''' - given the hash rate in Khps, calculate expected BTC generation per day and per hour, at current difficulty.
* '''bc,gend''' - given the hash rate in Khps, and a difficulty level, calculate expected BTC generation per day and per hour at that difficulty.
* '''bc,hextarget''' - show the current difficulty target in hex.
* '''bc,nethash''' - current 3-day estimate of network hash power, in Ghps.
* '''bc,nexttarget''' - show the block at which the next difficulty change will take place
* '''bc,interval''' - show the average time between blocks, over the past 1000 blocks. If given optional integer argument, use that many blocks for the estimate.
* '''bc,prob''' - show the probability of getting at least one block at given Khps, in a given time period. E.g., to see probability of getting a block at 1000 Khps, in 2 years and 1 week, try 'bc,prob 1000 2y 1w'. Time takes input in years, weeks, days, hours, minutes, and seconds.
* '''bc,probd''' - show the probability of getting at least one block at given Khps, given difficulty, in a given time period. Same as '''bc,prob''' but supply a difficulty after the hash rate. E.g., 'bc,probd 10000000 600000 1w 2d'
* '''bc,spotestimate''' - current 3-day estimate of network power, in terms of difficulty.
* '''bc,stats''' - show some statistics about the block chain - number of blocks, difficulty, estimated next difficulty target, time to next difficulty
* '''bc,timetonext''' - show estimated time to reach the next difficulty target
* '''bc,totalbc''' - show total number of bitcoins in existence.

Big kudos goes out to theymos for providing a web interface to [http://blockexplorer.com/q/ real time statistics about the bitcoin block chain].

===Markets and exchange rates===

* '''bc,bcm''' - show the market snapshot from bitcoinmarket.com
* '''bc,mtgox''' - show the market snapshot for mtgox.com
* '''bc,avgprc''' - show average 24h, 7d, and 30d trading prices of BTC in various currencies.
* '''bc,24hprc''' - show average 24h price of BTC in USD.
* '''bc,convert''' - convert bitcoin price, based on MtGox last, to currency you specify. e.g., try 'bc,convert eur' for euros.
* '''bc,fx''' - show various currency exchange rates
* '''bc,xau''' - show price of gold in BTC
* '''ticker''' - show pretty-printed mtgox ticker. Takes optional argument of '--bid', '--ask', '--last', '--high', or '--low', to show just that numeric value (useful for command nesting in calculations)
* '''bids''' - given a numeric argument, shows how many total btc are being demanded on MtGox at or over the given price. If optional '--under' argument given, looks under the price.
* '''asks''' - given a numeric argument, shows how many total btc are being offered on MtGox at or below given price. If optional '--over' argument given, looks over the price.

===Mining pool statistics===

* '''bc,slushpool''' - show the mining hash rate of the [http://mining.bitcoin.cz slush mining pool], in Khps.
* '''bc,eligius''' - show the mining hash rate of the Eligius mining pool, in Khps
* '''bc,swepool''' - show the mining hash rate of the Swepool mining pool, in Khps
* '''bc,btcguild''' - show the mining hash rate of the Btcguild mining pool, in Khps
* '''bc,deepbit''' - show the mining hash rate of the Deepbit mining pool, in Khps

===Other===

* '''bc,help''' - show list of 'bc,' commands - same as 'apropos bc'.
* '''bc,wiki''' - fetch a link to a page in this wiki, based on a search string. For example, to see a link to this page, try 'bc,wiki gribble'.

===bitcoin-otc related info===

* See [http://wiki.bitcoin-otc.com/wiki/Using_bitcoin-otc OTC guide] about using the order book
* See [http://wiki.bitcoin-otc.com/wiki/GPG_authentication OTC GPG guide] about using the gpg authentication system
* See [http://wiki.bitcoin-otc.com/wiki/OTC_Rating_System Web of Trust guide] about using the rating system/web of trust

===General commands===

The above list is specifically for bitcoin-related commands. See [http://sourceforge.net/apps/mediawiki/gribble/index.php?title=Using_Gribble_on_Sourceforge this page] for list and help of most commonly used non-bitcoin-related gribble commands. You can find more helpful info on the [http://gribble.sourceforge.net/ gribble] project page, or by exploring the bot with 'list' and 'help' commands.

==References==
<references />

==Factoids==

* [http://gribble.dreamhosters.com/viewfactoids.php?db=%23bitcoin-dev factoids for #bitcoin-dev channel]
* [http://gribble.dreamhosters.com/viewfactoids.php?db=%23bitcoin-otc factoids for #bitcoin-otc channel]

==Examples==

<me> ;;bc,blocks
<gribble> 96009

<me> Check out the current difficulty! ,,bc,diff
<gribble> 8078.19525793

<me> Here is a list of all gribble bitcoin commands: ,,(apropos bc)
<gribble> Alias bc,bcm, Alias bc,blocks, Alias bc,btcex, Alias bc,calc, Alias bc,diff, Alias bc,estimate, Alias bc,mtgox, Alias bc,nexttarget, Alias bc,stats, Alias bc,timetonext, and Alias bc,totalbc

<me> ;;list
<gribble> Admin, Alias, Anonymous, [...]

<me> ;;list Alias
<gribble> ?, about, add, bc,bcm [...], sfwikisearch, sl, slap, smack, [...]

<me> ;;sl bitcoin
<gribble> http://www.bitcoin.org/ | Bitcoin is a peer-to-peer digital currency. Peer-to-peer (P2P) means [...]

<me> Some commands have more than one argument. Surround with parens.
<me> e.g., Is your wallet safe? ,,(bc,wiki secure wallet)
<gribble> https://en.bitcoin.it/wiki/Securing_your_wallet | Apr 6, 2011 ... However a few [...]

<me> ;;calc 25 USD in EUR
<gribble> 25 US dollars = 17.2248 euros

===list of commands===

?, about, action, add, alert, alias, announce, announce add, announce list, announce remove, any, aol, apply, apropos, asks, at, auth, author, azn, ban add 
ban list, ban remove, base, bashorg, bc,24hprc, bc,avgprc, bc,bcm, bc,blocks, bc,btceur, bc,btcgbp, bc,btcguild, bc,btcrub, bc,calc, bc,calcd, bc,channels, bc,convert, bc,deepbit, bc,diff, bc,diffchange, bc,eligius, bc,estimate, bc,fx, bc,gen, bc,gend, bc,help, bc,hextarget, bc,interval, bc,mtgox, bc,mtgoxask, bc,mtgoxbid, bc,mtgoxlast, bc,nethash, bc,nexttarget, bc,price, bc,prob, bc,probd, bc,slushpool, bc,spotestimate, bc,stats, bc,swepool, bc,timetonext, bc,totalbc, bc,wiki, bc,xau, bids, binary, blockmonitor, bold, book, bot, botsnack, boturl, botweb, buy 
cache, calc, call, cand, capabilities, capability add, capability list, capability remove, capability set, capability setdefault, capability unset, capitalize, ceq, change, changekey, changename, channel, channeldb, channels, channelstats, check, cheer, chr, cif, clearq, cmd, coin, collect, color, colorize, command, commands, concat, config, configure, connect, contributors, convert, cor, countargs, cpu, crypt, ctell, ctime, cut, cxor, cycle 
decode, default, defaultcapability, defaultplugin, dehalfop, deleteuser, deop, devoice, dice, dict, dictionaries, direct, disable, disconnect, dns, do, doctype, driver 
eauth, ebay, echo, ed, eightball, elapsed, enable, encode, environ, eregister, errno, eval, everify, exec, exn, export 
factlist, facts, feed, fetch, field, fight, fit, flush, forget, format, fortune 
ge, get, getprefix, getrating, gettrust, ghost, give, giveme, giveout, gnu, google, gribble, gt 
h, halfop, headers, hebrew, help, hexip, hexlify, histsearch, hostmask, hostmask add, hostmask list, hostmask remove, hug 
icalc, ident, identify, ignore, ignore add, ignore list, ignore remove, info, insert, invite, ircquote, isitdown 
jeffk, join 
kban, key, kick 
last, latency, le, learn, leet, len, levenshtein, limit, list, lithp, load, lobotomy add, lobotomy list, lobotomy remove, lock, logmark, lower, ls, lt, lucky 
match, md5, mode, moderate, monologue, more, morse, mp 
names, nceq, ne, net, netcraft, networks, nge, ngt, nick, nicks, nle, nlt, nne, notes, notice 
oobhresponse, op, ord, otc, outfilter 
part, password, pet, petuser, pgp, phonebook, pid, ping, plugin, plugins, pong, private, processes, progstats 
quit 
rainbow, random, rank, rate, rated, re, reconnect, redo, refresh, register, reload, remove, rename, reorder, repeat, replace, replies, reply, repr, restore, reverse, rot13, roulette, rpn, rss 
sample, say, scramble, search, seconds, seen, sell, sendquote, separator, server, set, set password, set secure, settrace, sfideasearch, sflaconica, sfticketsearch, sfuserpage, sfwikisearch, sha, show, shrink, shuffle, simpleeval, since, size, sl, slap, slogan, smack, soundex, source, spell, spellit, squish, start, stats, status, stop, stripcolor, success, sudo, suicide, supa1337, swap, synonym 
targetproject, tell, texthelp, threads, ticker, time, title, tn,blocks, tn,diff, topic, translate, trustinfo 
ud, unauth, unban, unbinary, underline, undo, <gribble> undup, unhexlify, unidentify, units, uniud, unload, unlock, unmoderate, unmorse, unrate, unregister, unrename, unsettrace, until, upkeep, upper, uptime, urlquote, urlunquote, user, username 
vacuum, verify, version, view, voice 
whatis, whoami, whois, wk, wp, wtf 
xor 
yt

Template:Freenode IRC

2011-05-31T04:54:01Z

Da2ce7: Made Webchat TLS

[irc://irc.freenode.net/{{{1}}} IRC] [https://webchat.freenode.net/?channels={{{1}}}&uio=d4 Web] {{#if: {{{text|}}} | {{{text}}} | <nowiki>#</nowiki>{{{1}}}}}

Meetups

2011-05-27T10:48:42Z

Da2ce7: Added Melbourne

Don't add everyone who's going the the "Who?" column, just prominent bitcoin members and organizers.

{| class="wikitable"
|-
! Group
! When?
! Where?
! Who?
! Other Notes
|-
|
| 7:00 PM, June 16
|
| Boston, MA
|
|-
| [http://www.meetup.com/bitcoin New York Bitcoin Users]
| 7:00 PM, 2nd Saturday of every month
| OnlyOneTV Studios - 290 Fifth Ave New York, NY
| Bruce Wagner (Organizer) and others
|
|-
| [http://www.meetup.com/BitcoinDC Washington, DC Bitcoin Users]
| 7:00 PM, 1st Monday of every month
| Northside Social, 3211 Wilson Blvd Arlington, VA
| Darrell Duane (Organizer) and others
|
|-
| [http://www.meetup.com/Silicon-Valley-Bitcoin-Users Silicon Valley Bitcoin Users]
| 7:00 PM, Tuesday, May 10, 2011
| Sunnyvale Art Gallery Cafe, 251 W El Camino Real Sunnyvale, CA
| Brian Mcqueen and others
|
|-
| [http://www.meetup.com/BitcoinChicago Chicago]
| No regular schedule yet ([http://www.meetup.com/BitcoinChicago/events/past past meetings])
| Sunnyvale Art Gallery Cafe, 251 W El Camino Real Sunnyvale, CA
| Igor
|
|-
| [http://www.meetup.com/denver-bitcoin Denver]
| First meeting June 4th, 2011 ([http://www.meetup.com/denver-bitcoin/events/past past meetings])
| Gypsy House Cafe - 1279 Marion St Denver, CO
| bearbones
|
|-
| [http://www.meetup.com/bitcoinSF Bitcoin SF]
| Saturday, June 4, 2011 ([http://www.meetup.com/bitcoinSF past meetings])
| SFSU - 1600 Holloway Ave. San Francisco, CA
| Brian Mcqueen and others
|
|-
| [http://www.meetup.com/Los-Angeles-Digital-Currency-Innovators-Group Los Angels Digital Currency Innovators]
| Forming
| Suggest a location, and a date and time
| [[User:sgornick|Stephen Gornick]] (Interim organizer) and others
| Seeking meetup coordinator
|-
| [http://www.meetup.com/Las-Vegas-Bitcoin-Users Las Vegas Bitcoin Users]
| Forming
| Suggest a location, and a date and time
| Mark Russell
|-
| [[Melbourne Bitcoin Community]]
| Forming
| Suggest a location, and a date and time
| @da2ce7 on Freenode Channel: #bitcoin-aus
|
|-
| [[Bitcoin:Tokyo meetup|Tokyo]]
|
|
| [[User:MagicalTux|Magical Tux]] (Organizer) and others
|
|-
| [http://meetup.com/Bitcoin-Vancouver Vancouver Canada]
| Forming (1st meeting 23 May 2011)
| The Brickhouse - 730 Main St.
| humble (and others)
|
|-
| [http://www.bitcoin.org/smf/index.php?topic=6725.0 Zurich Switzerland]
| Semi-regular, about once a month
| Oliver Twist Pub
| Stefan Thomas (weusecoins), Mike Hearn (bitcoinj), bitdragon, Luzius (Wuala), more ...
|
|}

IRC channels

2011-05-27T10:43:25Z

Da2ce7: add #bitcoin-aus

The following Bitcoin-related IRC channels are available on [http://www.freenode.net Freenode]:

{| class="wikitable"
! Channel !! Description
|-
| {{Freenode IRC|bitcoin}} || General Bitcoin-related discussion.
|-
| {{Freenode IRC|bitcoin-otc|text=[[bitcoin-otc|#bitcoin-otc]]}} || Over-the-counter off-topic-chat.
|-
| {{Freenode IRC|bitcoin-pit}} || Only over-the-counter trading.
|-
| {{Freenode IRC|bitcoin-market}} || Streaming market data (only), no chat.
|-
| {{Freenode IRC|bitcoin-watch|text=[[Bitcoin-Watch|#bitcoin-watch]]}} || Streaming Bitcoin transactions, including market data.
|-
| {{Freenode IRC|bitcoin-dev}} || Bitcoin software development.
|-
| {{Freenode IRC|bitcoin-mining}} || Discussion and support related to mining.
|-
| {{Freenode IRC|bitcoin-politics}} || Discuss politics with other Bitcoin users.
|-
| {{Freenode IRC|bitcoin-aus}} || Aussie bitcoin community.
|-
| {{Freenode IRC|eligius}} || [[Eligius]] pool community
|}

IRC channels

2011-05-26T15:59:06Z

Da2ce7:

The following Bitcoin-related IRC channels are available on [http://www.freenode.net Freenode]:

{| class="wikitable"
! Channel !! Description
|-
| {{Freenode IRC|bitcoin}} || General Bitcoin-related discussion.
|-
| {{Freenode IRC|bitcoin-otc|text=[[bitcoin-otc|#bitcoin-otc]]}} || Over-the-counter off-topic-chat.
|-
| {{Freenode IRC|bitcoin-pit}} || Only over-the-counter trading.
|-
| {{Freenode IRC|bitcoin-market}} || Streaming market data, no chat.
|-
| {{Freenode IRC|bitcoin-watch}} || Another streaming market data channel.
|-
| {{Freenode IRC|bitcoin-dev}} || Bitcoin software development.
|-
| {{Freenode IRC|bitcoin-mining}} || Discussion and support related to mining.
|-
| {{Freenode IRC|bitcoin-politics}} || Discuss politics with other Bitcoin users.
|}

IRC channels

2011-05-26T15:58:38Z

Da2ce7: That is a bit more clear!

The following Bitcoin-related IRC channels are available on [http://www.freenode.net Freenode]:

{| class="wikitable"
! Channel !! Description
|-
| {{Freenode IRC|bitcoin}} || General Bitcoin-related discussion.
|-
| {{Freenode IRC|bitcoin-otc|text=[[bitcoin-otc|#bitcoin-otc]]}} || Over-the-counter off-topic-chat.
|-
| {{Freenode IRC|bitcoin-pit}} || Strictly over-the-counter trading.
|-
| {{Freenode IRC|bitcoin-market}} || Streaming market data, no chat.
|-
| {{Freenode IRC|bitcoin-watch}} || Another streaming market data channel.
|-
| {{Freenode IRC|bitcoin-dev}} || Bitcoin software development.
|-
| {{Freenode IRC|bitcoin-mining}} || Discussion and support related to mining.
|-
| {{Freenode IRC|bitcoin-politics}} || Discuss politics with other Bitcoin users.
|}

IRC channels

2011-05-26T15:49:41Z

Da2ce7:

The following Bitcoin-related IRC channels are available on [http://www.freenode.net Freenode]:

{| class="wikitable"
! Channel !! Description
|-
| {{Freenode IRC|bitcoin}} || General Bitcoin-related discussion.
|-
| {{Freenode IRC|bitcoin-otc|text=[[bitcoin-otc|#bitcoin-otc]]}} || Over-the-counter marketplace. (Off Topic Chat)
|-
| {{Freenode IRC|bitcoin-pit}} || Marketplace with low tolerance for off-topic chat.
|-
| {{Freenode IRC|bitcoin-market}} || Streaming market data, no chat.
|-
| {{Freenode IRC|bitcoin-watch}} || Another streaming market data channel.
|-
| {{Freenode IRC|bitcoin-dev}} || Bitcoin software development.
|-
| {{Freenode IRC|bitcoin-mining}} || Discussion and support related to mining.
|-
| {{Freenode IRC|bitcoin-politics}} || Discuss politics with other Bitcoin users.
|}

Template:MainPage Topics

2011-05-24T02:57:50Z

Da2ce7: added Donation-accepting_organizations_and_projects

{|cellpadding="2" style="background-color: inherit;"
|-
| scope="col" style="width: 200px;" |
* [[Introduction]]
* [[Getting started]]
* [[Securing your wallet]]
* [[Secure Trading|Best practices for traders]]
| scope="col" style="width: 200px;" |
* [[PHP developer intro]]
* [[API reference (JSON-RPC)]]
* [[Protocol specification]]
* [[Myths]]
|}

{|cellpadding="2" style="background-color: inherit;"
|-
! scope="col" style="width: 200px;" |
! scope="col" style="width: 200px;" |
|-
|
* [[:Category:Clients|Clients]]
* [[:Category:Mining|Mining]]
* [[:Category:Exchanges|Exchanges]]
* [[Press]]
|
* [[:Category:Technical|Technical articles]]
* [[:Category:Economics|Economics]]
* [[Trade|Bitcoin-accepting sites]]
* [[Donation-accepting_organizations_and_projects|Donation-Accepting Organizations and Projects]]
* [[Meetups]]
|}

<div style="text-align: right;" class="noprint">[{{fullurl:Template:MainPage_Topics|action=edit}} '''Edit'''] – '''[[Special:Categories|See More]]'''</div>

Template:MainPage Topics

2011-05-20T04:22:14Z

Da2ce7: Removed Outstanding Bitcoin Bounties - not maintained

{|cellpadding="2" style="background-color: inherit;"
|-
| scope="col" style="width: 200px;" |
* [[Introduction]]
* [[Getting started]]
* [[Securing your wallet]]
* [[Secure Trading|Trading Best Practices]]
* [[Myths]]
| scope="col" style="width: 200px;" |
* [[PHP developer intro]]
* [[API reference (JSON-RPC)]]
* [[Protocol specification]]
|}

{|cellpadding="2" style="background-color: inherit;"
|-
! scope="col" style="width: 200px;" |
! scope="col" style="width: 200px;" |
|-
|
* [[:Category:Clients|Clients]]
* [[:Category:Mining|Mining]]
* [[:Category:Exchanges|Exchanges]]
* [[Press]]
|
* [[:Category:Economics|Economics]]
* [[Trade|Bitcoin-accepting sites]]
* [[Meetups]]
|}

<div style="text-align: right;" class="noprint">[{{fullurl:Template:MainPage_Topics|action=edit}} '''Edit'''] – '''[[Special:Categories|See More]]'''</div>

Template:MainPage Topics

2011-05-20T04:21:27Z

Da2ce7: Removed BitCoin Registration from Topic Central // Not a real page.

{|cellpadding="2" style="background-color: inherit;"
|-
| scope="col" style="width: 200px;" |
* [[Introduction]]
* [[Getting started]]
* [[Securing your wallet]]
* [[Secure Trading|Trading Best Practices]]
* [[Myths]]
| scope="col" style="width: 200px;" |
* [[PHP developer intro]]
* [[API reference (JSON-RPC)]]
* [[Protocol specification]]
|}

{|cellpadding="2" style="background-color: inherit;"
|-
! scope="col" style="width: 200px;" |
! scope="col" style="width: 200px;" |
|-
|
* [[:Category:Clients|Clients]]
* [[:Category:Mining|Mining]]
* [[:Category:Exchanges|Exchanges]]
* [[Press]]
|
* [[:Category:Economics|Economics]]
* [[Trade|Bitcoin-accepting sites]]
* [[Active Bounties|Outstanding Bitcoin Bounties]]
* [[Meetups]]
|}

<div style="text-align: right;" class="noprint">[{{fullurl:Template:MainPage_Topics|action=edit}} '''Edit'''] – '''[[Special:Categories|See More]]'''</div>

Bitcoin Transport Layer API

2011-05-15T13:36:41Z

Da2ce7:

from post on bitcoin forum:

The BtcFn (The Bitcoin Freeent Project) project is in the process of working on the API connecting to the bitcoin client to other transport layers / data back-ends.

These backed layers will be used to transmit various bitcoin data over different protocols, such possible uses could be:
* Program that saves and reads a copy of the block-chain from a file. Say used to save the block-chain on a USB key-drive.
* A radio station could transmit the block-chain over short-wave radio so that everyone in the world has access to it. The same API could be used for a program to automatically import the block-chain updates in the Bitcoin software.
* BtcTorrent, a simple application that takes advantage of the API and lib-torrent that allows new clients to quickly download the block chain.
* The above mentioned bitcoin on freenet project, this project will allow clients to use bitcoin with freenet as a transport layer, for both transmission of the block chain, and transactions.
* Traditional bitcoin transport layer application. This application will implement the standard bitcoin p2p protocol, and will be used by default.

The API should be designed so that multiple applications can connect to the same bitcoin instance at the same time. The API should be non-blocking and atomic in design... (either something works completely, or it fails completely). Finally the API should have no access to any function that interacts with the wallet.

The goal is that every bitcoin implementation will implement this API, so any bitcoin implementation can use any transport implementation. e.g. Bitcoinj could make use of the same Bitcoin p2p application as the mainline client.

Questions/Comments?

We will be working on the design on the bitcoin wiki: (address to be added)

Bitcoin Transport Layer API

2011-05-15T13:36:00Z

Da2ce7: First Post

from post on bitcoin forum:

The BtcFn (The Bitcoin Freeent Project) project is in the process of working on the API connecting to the bitcoin client to other transport layers / data back-ends.

These backed layers will be used to transmit various bitcoin data over different protocols, such possible uses could be:

Program that saves and reads a copy of the block-chain from a file. Say used to save the block-chain on a USB key-drive.
A radio station could transmit the block-chain over short-wave radio so that everyone in the world has access to it. The same API could be used for a program to automatically import the block-chain updates in the Bitcoin software.
BtcTorrent, a simple application that takes advantage of the API and lib-torrent that allows new clients to quickly download the block chain.
The above mentioned bitcoin on freenet project, this project will allow clients to use bitcoin with freenet as a transport layer, for both transmission of the block chain, and transactions.
Traditional bitcoin transport layer application. This application will implement the standard bitcoin p2p protocol, and will be used by default.

The API should be designed so that multiple applications can connect to the same bitcoin instance at the same time. The API should be non-blocking and atomic in design... (either something works completely, or it fails completely). Finally the API should have no access to any function that interacts with the wallet.

The goal is that every bitcoin implementation will implement this API, so any bitcoin implementation can use any transport implementation. e.g. Bitcoinj could make use of the same Bitcoin p2p application as the mainline client.

Questions/Comments?

We will be working on the design on the bitcoin wiki: (address to be added)

User:Da2ce7

2011-04-24T05:25:35Z

Da2ce7:

Contributors Award participant: 1MFrb1UwEVUg1KeKixnZTiRzLmCuSGUyqN

<pre>
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v2.0.17 (MingW32)

mQMuBE1NLOgRCACgarx+ESnLTcIYI9og3Ar8ixSwfHX27tig1AVWfBRKBV9C2Txy
xFv3gcIe0f2ZZvKpnwutBgES3xts8bAqJ5zU1wQQMEdwj5CyphuYuyl7PLO/+F3p
1aIZNdw8BayRWTDlLLY2SJ3h5S9oTO0WPNLspViaztto6nXgLS1TBQ5cFBoag+aK
nQbarWotLcsnOZBUhKQqxh0UViO9Mfuce483Bd+oF34NtTRdQyUjysqVpl3n5joe
NK/HhwSgqhzOHhU3BDy6IWXvJZJD3NFXmGrMZKVUdSPDNsNNBz+d9NV+69BMw4IT
g8XdeH+Kxoj/wpzisTH6XDMkkW7TDlj80UoLAQDvICVl1LPPUaCJZmDtrTVBdlVi
uT2LJTQ0TG3TxfN0yQf/aLyIhO/UrogQ3orJp1mJQokOb5IRhhqHzHxUBr6tzYD3
rclArlGDHqnzUK6tYJb5Pj3egLeuMZekt2nv44C6HVhDwRijfpUVW6cSgAKG2Pqf
5RfPINUFLpq0QVhvvMEPR5ah6KLPyPWL6YcDXOGZPGAUZnxOepN4quCyDYh9zp9G
bEZbztAGLaH0UrE+ELZWj39zyx3wNpgW037ZeoUr8HrEUsm5uyYkpnR/MC3KYWvo
kJSPLLl3fR3LEyqTq8SwjoVrjIVwH1q6CFQGsNpVsd7NK6MGR4aXFj1RXaf58LHB
xhkYOo4EHvl3SegmJEj3Kiahn9VhBqg9XSvJvE2X3gf+OTV/Jn82v41UlBfZ+O2D
LCmGLvdvI9fv/d+7ZcZWFINiTu3XXtpQIpYng7V7p4nTaIhlnRj7ux8xZH/A1e6u
dmoiWHvwhEczW+zwr0fNAOSCKMirKqXVtyLirmVbJqiUPJNewRqN1ZJc0P4SK3JT
xQPKoR1pu7kLvGEUGZLZMwlRNzK1TPfkqlDELEwMn49HCNxxG+mYvXRsIKfJkMjf
csxUyrkzXsWhM60tzp02EIxFovJ/Yl+7jnLdO+SxdiaC5XhQ00y/QTpDj5iX8NNn
IiWDZTs1a2WW+RI1z4fsCzx+n/2E/oJOMFop6tFywzB7+v/t5FB/cAnDoRcI9Vxh
ZrQiQ2FtZXJvbiBHYXJuaGFtIDxkYTJjZTdAZ21haWwuY29tPoiABBMRCAAoBQJN
TSzoAhsDBQkDwyyoBgsJCAcDAgYVCAIJCgsEFgIDAQIeAQIXgAAKCRAEnxwwM7Xn
1oquAPwO3ZIxNrHNLAi7YqFWN77AtJjqtuBv6A6iG6gKTlZg0wD9GYbkcwNa7S2+
x7RHAnei6/zEZkhq+3p8AmGeyiXXmp+IRgQQEQIABgUCTW8JeAAKCRDn+Ti+yVWU
sjfsAKCT/qCslYlmtf1I9ouh1DUpiyLJYwCff8geJUzTZ2/Z0ZtxR6BYQCf8Q0O5
Aw0ETU0s6BAMAOFSgL3xCHmBUCKISWqrRyxJmqGmO/MaM8hUeLj5JmW46/THBfWY
KUPcDU+1yBXV1u65Ywxz8954UTgipg+sA9ydaf+hSVRA7wgtVlOVWtFiy9pYLZ0S
Ksr0QkHpl0JSzQ9CdXomExm4cTOlAE+tOx0PnZ6cbzq0gdalPgjNJazhy5yS312r
apLs2ddPS2xSBdeu3iYV+4iK/Sx87RwVcj4qzmzG6w3eHLxDs6PZE3EHSdlAVqUM
UEIDuLsflsF3o5v3UaW2OIfesuzKoRIuwWa0djhZ9NIyLcSUE95NDAr2qXq3Akti
FTjIljWh/YgZGASdB/QDnWwYzjdPFJvAQw8+8gMc3ypFAzdQ2rlvx0BEHmRMdKn4
BKr0C1bS2AwirSfQUMxhOung+usHw3jQjPsqSh6wkrm51HlPwf2SI0jsopR2YZsd
pk4Q/edQHx5EJprVTgNTvloFG2ui3UEA7MZa2TubzLpEk+NeP1GDOVpweRNoqqaw
c1NjQd8SGDun7wADBwv/WjfySo0iuLHwwGJGIc1EmMpTDBl8Vl8NCHZ9jM6mdMp0
WMhQ+OU3KtOAeYPVMLYYaZTcMZjH0Jd0WuBlIbvTAhOMZSBYFIyzPOFqIhbQvnig
mKbpzMDguNp/2b4HBmqgwOHOr/YGauFrQ5Vos2TynAIhTktRvOvb1CYjcyqHqqxk
DZWlHWx9DqKvGXJpDKwPmAUIsWPDRdXyI7ElJk6/FNnuG8B/L5Vnwtu45qYzWp68
9+SkIGWlD+IWRKF7kyiXyKtSHNcHz6aMLY3jjraglZJHkutuW5B4ojKzglKkP9Q3
eMFX33qInnWQaz+lpoGmRfPQ9ALMqQrnwM28eqHi9p3wP7rUHjs9FxurxILIY29U
2SuwFUm6+n305ufYTQR2SHR9pDB2gD89Wi6q60AY5tQQfc90RWXp4PMwus82WdyS
jyHN0rpyAj/M9q99bdemWBq1TReGOXdczDs53kQui5MO21zMXejgGQGhcg3D8yYB
vAtDe8lmmw19X1nqrUaZiGcEGBEIAA8FAk1NLOgCGwwFCQPDLKgACgkQBJ8cMDO1
59b9uAEA1zlKSl/vE0u0rYEmMXzqFYfDdN17EVVNvgTOTmh2/VkBALZmprCwWDcn
oj0Qwu3RJI9eHlspmZ6yNa+Um+EsKaA9
=Mb8Q
-----END PGP PUBLIC KEY BLOCK-----
</pre>

Deflationary spiral

2011-04-24T05:18:35Z

Da2ce7:

'''Deflationary spiral''' is an economic argument that proposes that a runaway deflation would eventually lead to the collapse of the currency. It is a common criticism made against the viability of [[Bitcoin]].
The ‘deflationary spiral’ is a real condition that affects the fiat fractional reserve backing system. Bitcoin is not affected by this because it is fundamentally different to fiat currency. 

Deflationary spiral occurs when the price of a traded article increases at some given rate which causes people to hoard it. As people hoard the commodity, less and less of it is available thus causing the price to go up even more. In turn, even more people hoard the commodity. Thus a feedback loop or spiral of deflation occurs. 

In practice, there is only a limited amount of 'value' that can be placed upon a good before it becomes too attractive to trade for other goods (thus ending the spiral). The only time that the 'Deflationary Spiral' can happen (to it's conclusion) is when people can foresee a time where they are forced to use that particular traded article.

==In The Fiat Fractional Reserve Banking System==
The fiat money that we trade consists of the principle of the loans of other people. All this money must be someday 'repaid.' When people save (pay back their loans), the total monetary supply is contracting. When people spend (take out loans), the total monetary supply is increasing.

If you have people who are hoarding money, the principle still need to be repaid. Hoarding will make it harder for other people in the economy to pay back their loans.

Becasue people foresee a time where they need to pay back their loans (a future fixed expense), when the value of the money starts to increase (deflation), those with loans will endeavour to pay back the loans quicker. This causes the monetary supply to reduce, reducing the total amount of money available for repayment of loans, again making it harder for people to pay back what they owe.

This Deflationary spiral diverts funds away from the legitimate economy, to the repayment of debt. Causing the economy to stagnates and stop.

==Bitcoin==
The key difference is that people don't foresee a fixed cost (unit amount) that they must pay with Bitcoin. If the value of the Bitcoins that they own increases, then any future cost will take a proportionality smaller amount of Bitcoin. There isn't any fixed incentive to holding Bitcoin other than speculation.

If the economy that uses Bitcoin grows, the per-unit value of Bitcoin proportionally increase also.

Everything is the opposite to the fiat fractional reserve banking system (because Bitcoin isn't a debt but an assist). Bitcoins '''only''' deflate in value when the Bitcoin Economy is '''growing'''.

Becasue the Deflationary spiral is a real problem in the traditional monetary system, doesn't necessitate that it can also be a problem in the Bitcoin economy.

==See Also==

* [[Controlled inflation]]

[[Category:Economics]]

Deflationary spiral

2011-04-24T05:16:15Z

Da2ce7:

'''Deflationary spiral''' is an economic argument that proposes that a runaway deflation would eventually lead to the collapse of the currency. It is a common criticism made against the viability of [[Bitcoin]].
The ‘deflationary spiral’ is a real condition that affects the fiat fractional reserve backing system. Bitcoin is not affected by this because it is fundamentally different to fiat currency. 

Deflationary spiral occurs when the price of a traded article increases at some given rate which causes people to hoard it. As people hoard the commodity, less and less of it is available thus causing the price to go up even more. In turn, even more people hoard the commodity. Thus a feedback loop or spiral of deflation occurs. 

In practice, there is only a limited amount of 'value' that can be placed upon a good before it becomes too attractive to trade for other goods (thus ending the spiral). The only time that the 'Deflationary Spiral' can happen (to it's conclusion) is when people can foresee a time where they are forced to use that particular traded article.

==In The Fiat Fractional Reserve Banking System==
The fiat money that we trade consists of the principle of the loans of other people. All this money must be someday 'repaid.' When people save (pay back their loans), the total monetary supply is contracting. When people spend (take out loans), the total monetary supply is increasing.

If you have people who are hoarding money, the principle still need to be repaid. Hoarding will make it harder for other people in the economy to pay back their loans.

Becasue people foresee a time where they need to pay back their loans (a future fixed expense, when the value of the money starts to increase (deflation), those with loans will endeavour to pay back the loans quicker. This causes the monetary supply to reduce, reducing the total amount of money available for repayment of loans, again making it harder for people to pay back what they owe.

This Deflationary spiral diverts funds away from the legitimate economy, to the repayment of debt. Causing the economy to stagnates and stop.

==Bitcoin==
The key difference is that people don't foresee a fixed cost (unit amount) that they must pay with Bitcoin. If the value of the Bitcoins that they own increases, then any future cost will take a proprietary smaller amount of Bitcoin. There isn't any fixed incentive to holding Bitcoin other than speculation.

If the economy that uses Bitcoin grows, the per-unit value of Bitcoin proportionally increase also.

Everything is the opposite to the fiat fractional reserve banking system (because Bitcoin isn't a debt but an assist). Bitcoins '''only''' deflate in value when the Bitcoin Economy is '''growing'''.

Becasue the Deflationary spiral is a real problem in the traditional monetary system, doesn't necessitate that it can also be a problem in the Bitcoin economy.

==See Also==

* [[Controlled inflation]]

[[Category:Economics]]

Deflationary spiral

2011-04-24T05:13:32Z

Da2ce7: Complete Change.

'''Deflationary spiral''' is an economic argument that proposes that a runaway deflation would eventually lead to the collapse of the currency. It is a common criticism made against the viability of [[Bitcoin]].
The ‘deflationary spiral’ is a real condition that affects the fiat fractional reserve backing system. Understanding why Bitcoin isn't affected by this problem you must first understand why it is a problem for our current system. 

Deflationary spiral occurs when the price of a traded article increases at some given rate which causes people to hoard it. As people hoard the commodity, less and less of it is available thus causing the price to go up even more. In turn, even more people hoard the commodity. Thus a feedback loop or spiral of deflation occurs. 

In practice, there is only a limited amount of 'value' that can be placed upon a good before it becomes too attractive to trade for other goods (thus ending the spiral). The only time that the 'Deflationary Spiral' can happen (to it's conclusion) is when people can foresee a time where they are forced to use that particular traded article.

==In The Fiat Fractional Reserve Banking System==
The fiat money that we trade consists of the principle of the loans of other people. All this money must be someday 'repaid.' When people save (pay back their loans), the total monetary supply is contracting. When people spend (take out loans), the total monetary supply is increasing.

If you have people who are hoarding money, the principle still need to be repaid. Hoarding will make it harder for other people in the economy to pay back their loans.

Becasue people foresee a time where they need to pay back their loans (a future fixed expense, when the value of the money starts to increase (deflation), those with loans will endeavour to pay back the loans quicker. This causes the monetary supply to reduce, reducing the total amount of money available for repayment of loans, again making it harder for people to pay back what they owe.

This Deflationary spiral diverts funds away from the legitimate economy, to the repayment of debt. Causing the economy to stagnates and stop.

==Bitcoin==
The key difference is that people don't foresee a fixed cost (unit amount) that they must pay with Bitcoin. If the value of the Bitcoins that they own increases, then any future cost will take a proprietary smaller amount of Bitcoin. There isn't any fixed incentive to holding Bitcoin other than speculation.

If the economy that uses Bitcoin grows, the per-unit value of Bitcoin proportionally increase also.

Everything is the opposite to the fiat fractional reserve banking system (because Bitcoin isn't a debt but an assist). Bitcoins '''only''' deflate in value when the Bitcoin Economy is '''growing'''.

Becasue the Deflationary spiral is a real problem in the traditional monetary system, doesn't necessitate that it can also be a problem in the Bitcoin economy.

==See Also==

* [[Controlled inflation]]

[[Category:Economics]]

Deflationary spiral

2011-04-24T04:45:00Z

Da2ce7: /* Counterargument */

{{stub}}
'''Deflationary spiral''' is an economic argument that proposes that a runaway deflation would eventually lead to the collapse of the currency. It is a common criticism made against the viability of [[Bitcoin]].

Deflationary spiral occurs when the price of a commodity increases at some given rate which causes people to hoard it. As people hoard the commodity, less and less of it is available thus causing the price to go up even more. In turn, even more people hoard the commodity. Thus a feedback loop or spiral of deflation occurs.

==Effects==
Deflation, like inflation, includes winners and losers.

The losers are borrowers, especially those who would have to pay principle plus interest rate. Since the value of loan increase due to inflation, that means they will have to pay more in real term.

The winners include anybody who had saved. Thus, a deflationary environment would automatically encourage more people to save for the expectation of increasing purchasing power.

==Economic history==
The first deflationary phase in Bitcoin's economic history is a phase of economic growth caused by the slashdot effect. From there, we see the the price of bitcoin rose to 0.06 USD. This price level remain stable until early October, when a rally cause the price to touch .50 USD before settling at the .20-30 USD equilibrium.

There will only be 21 million bitcoin in the world, ever. Thus, the expected value of bitcoin rise in correlation with the number of people using it, as well increase in productivity. Further deflation occurs with people losing their wallet, thus all access to their bitcoin. While the destruction of bitcoin never occurs, the loss of key to access it effectively mean that bitcoin can never be used again.

Over the long term, as long as the combination of the two causes hold true, deflation will continue to an absurd level.

==Counterargument==
There is lots of confusion about this topic from modern-day economists. 

The ‘deflationary spiral’ is a real condition that affects the fiat fractional reserve back system. Understanding why Bitcoin isn't affected by this problem you must first understand why it is a problem for our current system. 

In our current monetary system there is no ‘money’ as an asset but a whole lot of ‘principle to loans.' When the money supply is contracting (deflation) people are paying back their loans. (or saving). The other thing is to understand is there is more loans (principle to be repaid) issued than ‘money,’ so when loans are paid back, the available money supply to pay back all the other outstanding loans gets smaller. 

When the economy is booming or growing, more and more people take out loans to fund their future endeavours, thus increasing the monetary supply. Because the economy is growing, this masks the real inflation (of the monetary supply). The deflationary spiral happens when people start saving because of a slowing or contracting economy. The money supply gets smaller (as the loans get paid off), finding money for repaying the remaining loads becomes disproportionally harder to find. 

People who hoard (are debt free) are making it harder for those who have loans to repay them. The loans get harder and harder to repay (the value of money goes up), and people start defaulting. Thus in the current economic system, dollars will become very expensive stopping people spending, slowing the economy. Not because they are saving (for future spending), but because they are paying back their loans (so they don't have to pay interest). 

Bitcoins are different. Bitcoins go up in value when the bitcoin economy grows, and go down in value when it contracts. Everything is the opposite to the fiat fractional reserve banking system (because bitcoin isn't a debt but an assist). Bitcoins '''only''' deflate in value when the Bitcoin Economy is '''growing'''. Becasue the Deflationary spiral is a problem in the traditional monetary system, doesn't necessitate that it can also a problem in the Bitcoin economy.

==See Also==

* [[Controlled inflation]]

[[Category:Economics]]