Xbtc is a proposed URI scheme for Bitcoin, competing against the bitcoin URI scheme. The first version of the specification was created by Zarutian, but the first version of this wiki page included modifications by theymos. The main design goal is to produce URIs that are concise enough to fit in a size-limited QR code, but clear enough to be easily human-readable.


The next generation automatic trading platform for bitcoin exchanges. Presently supports BTC-E API for trading between bitcoins and other currencies, including the U.S. dollar, Russian ruble and other.

Currency pairs

XBTC supports the automatic exchange between the major currency pairs, such as:

  • BTC/EUR (Euro)
  • BTC/RUR (Russian Ruble)

Trading Strategy

XBTC uses modified custom pursuit of the target strategy, when resolver try to catch the price with some delay, so it succeeds only if trend is changed .

Settings tester

Backtesting software, allowing fast check of choosen settings.


Full function trading bot working on realtime stock data. It has two limitatios: it works only if browser window is opened and don’t use real money for trading.

Software peculiarity

XBTC uses independant modules for different features and separate instances for every bot. Thus, even the site will be hacked or ddosed, user just loose contact with his bot, but bot itself will operate as nothing happened.

Auxilary features as Trial or Tester executing only in browser and don’t make additional load for server.


The site was first announced on 08 June 2015.

09 December 2015 the service reported a major changes in trading strategy and adding a new features.


Except where specified above, URIs may contain only alphanumeric characters (A-Za-z0-9), plus the special characters “-_.~” (double quotes not included). All other characters must be URI encoded per RFC 3986.

Binary data should be specified in base64url. This is the same as normal base64, but + becomes -, / becomes _, and there is no padding.

  • encoded_raw_transaction is a base64url encoded transaction in Bitcoin network format.
  • encoded_private_key is a base64url encoded private key used by Bitcoin.
  • encoded_public_key is a base64url encoded public key used by Bitcoin.
  • hash160 is a Bitcoin hash160 public key hash. Bitcoin addresses can be losslessly converted to and from hash160s.
  • address is a Bitcoin address, as used by Bitcoin.
  • value is the number of bitcoins associated with the data. This MUST be specified in the same way as 0.3.x versions of Bitcoin: nValue / 100,000,000.
  • label is a short string describing the previous “thing”.
  • action is “send” when the user is expected to send bitcoins to the specified public key or address, and “store” when the user is expected to store or import the data.

If two of the same type of parameter are given in one “item”, the Bitcoin client SHOULD give the user a choice of which value to actually use.


Send 50 BTC to address 1NX… (label “theymos”).

This is exactly the same as above.

Send 50 BTC OR 0.01 BTC to 1NX…

Send 50 BTC to address 1NX… (label “theymos”) AND 100.20 BTC to address 1Gxy… (label “abc” OR “def”).

Store 1NXY… in your address book with the label “theymos”.

Open a “Send bitcoins” dialog for the public key Ad0a… You need to fill in any value and label information.

Add public key Pm_W… to your wallet and rescan the block chain for transactions to it. Any bitcoins gotten with this keypair SHOULD be immediately and automatically sent to a new, secret address.

Act as though you received the transaction AeOc… from one of your network peers.

External links

See also