The Bitcoin Improvement Proposal that defines the Bitcoin URI scheme is BIP21.
The simple syntax is:
On the desktop all of Armory, Electrum and MultiBit respond to Bitcoin URI clicks in a browser and I believe Bitcoin-QT V0.7 does as well.
On mobiles Android ...
The value of a Satoshi is fixed.
The key word is "currently" (smallest currently possible).
If the divisibility is ever increased, a Satoshi will still be exactly 0.00000001 BTC, even though there exists unit representing an even smaller amount.
There would need to be new names for these new denominations that are even smaller than a Satoshi, but dSatoshi ...
Like Murch said, there isn't a current text based symbol for it, but if you're going to use it on a web application, you can always use Font Awesome.
After you include the fontawesome library, you use the bitcoin symbol like this:
<i class="fa fa-btc"></i> fa-btc
Example output of the code above would be:
You can find more information ...
I don't know about the rest of the string but I think the leading bytes are ordered that way to make the types of "addresses" be human reconizable.
From a quick look at the source I think the leading characters, rpshnaf map like so:
r = public Ripple address
p = node private
s = Ripple secret
h = ?
n = node public
a = address family generator or seed ?
f = ...
The system is using integers to represent amounts. 1 satoshi is the smallest unit (integer one). The satoshi is the base unit of the protocol (not the bitcoin).
It would be very hard to change this to support more decimals, but it seems also extremely unlikely that the need arises. With 21 millions bitcoins (i.e. 2,100,000,000,000,000 satoshi) in total, ...
The Bouncy Castle project allows for this and it runs on the Java VM (as was mentioned earlier) as well as the .NET Runtime. An example of using it in C# is shown in this blog post. You can use the .NET version from Visual Basic .NET (as well as any of the other languages on the CLR as well, obviously).
For C++, look at the Crypto++ library which supports ...
Bitcoin is the currency of the future.
In order to understand why this is true, there are two key pieces of information that a person must have:
The first is an understanding of how money actually works: how it is created, how it enters the marketplace, and what exactly makes it valuable.
The second is an understanding of the Bitcoin community and system.
Recently I stumbled across this question as I was supposed to explain what Bitcoin was to my 5-year-old nephew.
As the question states that it needs to explain the concept of bitcoin to a non-technical person, I took it a step further and explained it to the kid, who knows nothing (literally).
So here goes my 2 satoshis on what is the best explanation (...
The realistic, honest answer to this question is that Bitcoin is a "Digital Commodity".
Bitcoin cannot currently be described as a digital currency since it cannot, practically, fulfill the basic functions of a currency. The wildly fluctuating USD/BTC exchange rate alone means there is price instability. How would YOU like to offer your labour for a few ...
I got the common Bitcoin symbol (B with two lines) approved for addition to Unicode as U+20BF last year. It will hopefully become part of the next Unicode standard in June and then it can be used in text. The character (₿) is already supported by iOS and macOS.
This is the PR that made OP_RETURN outputs standard:
The current code:
if (GetBoolArg("-datacarrier", true))
The denial-of-service (DOS) attack is easy to explain: each time a transaction is updated by increasing the sequence number in an input, the whole transaction needs to be propagated through the network again. So if a transaction is 1 KB and there are 10,000 full nodes, you can waste a minimum of 10 MB of network bandwidth each time you update the ...
The Bouncy Castle library provides support for all languages on the Java VM
This library (and now a derivative library called Spongy Castle) is used in the BitCoinJ library.
The Bouncy Castle library was unfortunately implemented badly in Android which lead to code conflicts that required complex workarounds. Spongy Castle solved those problems making the ...
I think most people don't get the decentralized part. To explain, I have made a few questions and their answers:
how are bitcoins created?
how does it prevent double spending?
how do we avoid central authorities?
Bitcoin is a distributed ledger. Everyone knows how many bitcoins are around and which address sent how many to which address (sort of).
Bitcoin is a global payment network on the internet. It is self-sustained and allows users to make payments between individuals like cash.
Instead of a company being the referee, Bitcoin is governed neutrally by rules asserted through a network of computers running the same open-source software.
Bitcoin is completely transparent, in that anyone can see ...
There's a dedicated C-library for this curve. This is probably the most widely scrutinized library, and it probably has the best performance. Wrappers for other languages are available.
Update in 2020: The Unicode 10.0 release included the Bitcoin symbol ₿ as U+20BF. For your computer to show the symbol in text, you may need to install a font that includes it. For Linux, one such font is GNU Unifont Glyphs.
To my knowledge there doesn't yet exist a single symbol font representation of the B with two vertical lines, although it seems to be ...
I've made a custom font with Bitcoin, Litecoin, and Dogecoin symbols. There's a download link in .otf format in this bitcointalk thread. (It's labeled "Download.")
If this font file doesn't include a cryptocurrency symbol that you need, I'm willing to add it.
The Hash256 is essentially a uint256. However, after reading through much of the wiki and source, it appears that the Hash256 type is meant to be a generic, unsigned integer type that can store any form of hash that is larger than 128 bits.
As an example, all hashes mentioned in the Tree Formats portion of the wiki are stored in Hash256 fields. Some are ...
The ledger_index is the 256-bit index of a particular entry in the ledger. The ledger's state tree is a hash tree of index/value pairs. Each index is a 256-bit hash of some kind of locator. If the entry is, say, an account root node, the index is a hash of the 160-bit account ID. If the entry is, say, a ripple balance node, the index is a hash of the two ...
I put together a Kindle book, Bitcoin Step by Step, that covers some best practices. When I was writing I searched the web for what ever I could find trying to make sure what I suggested was indeed the current best practices. You can find it on Kindle.