Market Home
Client Software Version
Aquila uses client-side cryptography to resist theft of funds or disclosure of secret information, even if its servers are compromised. For full security, the Aquila client must be installed locally. If you don't install the client, then its security is no better than for a standard web application.
The client is a single HTML file, with no other dependencies. To install, right-click to download the file below, and save it to local media. Then open the file with your web browser.
| You Are Running | |
|---|---|
| Version: | |
| The Market Recommends | |
| Version: | |
| Download Link: | |
| File sha256 Hash: | |
The recommended software version is obtained from a message signed and broadcast by the market owners, and will change from time to time.
The client is distributed as a single HTML file instead of a browser extension because:
- JavaScript in an ordinary web page is more sandboxed than JavaScript in a browser extension, reducing the attack surface if this client turns out to be malicious or flawed.
- Installation of browser extensions is inconvenient on many operating systems designed to run from read-only media.
The client that you are running now is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
Copyright 2016 Aquila Developers
Private Messages
| From: | ||||
Messages older than are not shown, even if they're unread.
Private Messages
| From: | ||
| To: | ||
| Subject: | ||
| Bitcoin Tx: | pays to | |
| State: | ||
| make msg also readable by | ||
| (plain text, no markup) | ||
Upload Images
Uploaded images can be attached to listings. Existing images appear below.
| Image | Thumbnail |
|---|---|
Search Listings
| Category: | ||||
| Ship From: | Ship To: | |||
| Seller: | ||||
Address Book
Users on the market are identified by Bitcoin-style addresses (coded hashes of public keys). To keep track of people more conveniently, you can assign arbitrary nicknames to addresses.
Only you will see these nicknames. For security reasons, the market does not try to provide a global address book.
| Address: | ||
| Nickname: |
| Address (PK Hash) | Nickname | |
|---|---|---|
Forum List
| Name |
|---|
| Age | From | Subject |
|---|
Manage Keys
All users identify themselves to the market using cryptographic key pairs. The browser may store these key pairs persistently (across exit and reboot), but you should also back them up by exporting them to a file and saving it locally.
To import from a backup file, delete all keys below. You will then be prompted to import.
| PK Hash | Type | Secret Key (WIF) | Public Key (hex) | Age | Action |
|---|
| (type "DELETE ALL" in box to confirm) |
If you delete all keys, then you will lose the ability to decrypt messages sent to you, or to release escrowed funds. Do not rely on any delete button here to securely delete keys. Use encrypted volumes, and wipe or physically destroy media at end of life.
Delete Old Encryption Key
By deleting this key, you will make all messages encrypted with it permanently unreadable. These messages are:
Delete Old Pseudonym
By deleting this pseudonym, you will lose the ability to send new messages under this identity, or to release any escrowed funds. You will also lose access to any encrypted messages sent to this pseudonym. These messages are:
| Type | Hash | Age |
|---|
| (type "DELETE" in box to confirm) |
Create New Listing
| Currency: | |
| Ship From: | (like "DE", "FR,GB", "EU,CH", "ANY", etc.) |
| Ship To: | |
| Category: | |
| Title: |
(plain text, no markup)
Select images from the list below to attach to this listing. Images must already have been uploaded.
From the table below, the buyer must choose one line from the "main" group, and one line from the "shipping" group if it's present.
| Item Description | Price Each | Group | |
|---|---|---|---|
My Current Listings
| Title | Age | |
|---|---|---|
This listing has been deleted.
| Item | Price | Qty |
|---|
Shipping address, and notes to seller:
The multisig payment address will be generated after you broadcast the order, and exchange rates will be locked. Your order may be cancelled if you don't send payment within thirty minutes.
Orders
| Hash | Age | Title | Buyer | Seller |
|---|
View Existing Order
| Hash: | |
| Listing: | |
| Seller: | |
| Buyer: | |
| Age: | |
| Pay To: |
The buyer must send payment in the given amount to the Bitcoin address above. The seller will confirm that payment has been received, by clicking the address to view it in a blockchain explorer.
| Item | Qty | Price (Each) | Price (Total) |
|---|
The following private messages have been sent regarding this order:
Order Escrow Release
| Order: | |
| Seller: | |
| Buyer: | |
| Pay From: | |
| Value In: | |
| Pay To: | |
| Value Out: | |
| Fee: | |
| Transaction: |
Msg Explorer
| Hash: | |
| Type: | |
| Time: | to (Unix time, or -x for x days ago) |
| sigFrom: | (sender) |
| cipherTo[0]: | (intended recipient) |
| : | |
| Skip first: | results |
| Hash |
|---|
Market Control
Control of the market (i.e., the ability to allow or ban users, or moderate a forum, or release escrow to resolve a buyer-seller dispute) is determined by a vote of many owners, with ownership tracked in the Bitcoin blockchain.
The current elected admins are:
The owners are:
The owners have delegated voting power (agent : [ principal0, ... ]) as follows:
The ticker, which contains frequently-changing information needed by the client, is:
Owner Tools
This is a list of marketControl messages. Only one is effective, but many can be broadcast and awaiting votes. The message with greatest total voting power becomes effective after a delay, typically a few minutes.
| Hash | adminPkh[0] | Age | Voting Power | |
|---|---|---|---|---|
Compose and broadcast a marketControl message. All owner's keys that you control will vote for this message. In most cases, more votes from other users will be required before it becomes effective.
If you broadcast a proxy message, then the person that you specify can vote on your behalf on marketControl messages. Select an owner's key, and delegate or rescind proxy voting power:
| pkhId | Shares |
|---|
If you rescind the proxy, then they lose that authority.
Admin Tools
| Approve As: | |
| Address: | |
| Valid From: | (Unix time, or +/-x for x days in future/past) |
| Valid To: | |
| kB Per Day: | |
| Comment: |
| Hash: | |
| Comment: |
CSV format, one row per payment, "from,to,amount", amount in BTC.
My User Information
This page contains public information about you. For example, a seller might post general policies here, or off-market contact information. Other users will see this page when they click your address.
(plain text, no markup)
User Information
| User: | |
| Last Seen: | |
| Private Msg: | |
| Role: | seller buyer admin owner BANNED |
| Effective: | |
| Feedback: |
Provide Feedback
Leave a score of +1 after an entirely successful transaction, or -1 if you got scammed. A score of zero has the same effect as no feedback at all.
| Left By: | |
| For User: | |
| Order: | |
| Score: | |
| Comment: |
View Feedback
| Left By: | |
| For User: |
| Age | Left By | For | Comment | Score | Order |
|---|
Market Fees
Market fees are generally paid from sellers to owners, but may be used for other purposes too (e.g., to refund a bond posted by a seller). They are totally independent of payment for items bought and sold on the market.
Requests from the market admins to pay fees:
Confirmations from users claiming to have paid fees:
Stealth-style payment is used, so the fee recipient needs this confirmation to find the payment in the blockchain.
Requested Fee Payments
The admins have requested that users make payments as follows:
| From: | |
| To: |
| Hash | Age | By Admin | Comment |
|---|
Requested Fee Payment
In one specific payment request:
| Hash: | |
| Age: | |
| By Admin: | |
| Comment: |
| From | To | Value (BTC) |
|---|
Completed Fee Payments
Users claim to have made payments as follows:
| From: | |
| To: |
| Hash | Age | From | To | Value (BTC) |
|---|
Completed Fee Payment
A user claims to have made the following payment:
| Hash: | |
| Age: | |
| From: | |
| To: | |
| Amount: | |
| Request: | |
| Pay To: | |
| WIF: |
The sender must pay Bitcoin to the address given above, in the given amount.
The recipient may import this address as WIF to another wallet, and spend the payment from there.
Server List
The table shows the server URI, goodness metric, average response time, last seen time, whether it appears in marketControl, and whether it appears in the hard-coded bootstrap list.
| URI | Gdns | resp (s) | ago | mktC? | btstrp? |
|---|
Choose servers
CAPTCHA Required
Last CAPTCHA wrong, please retry.
No Keys in Browser Local Storage
No cryptographic key pairs were found in browser local storage. All market buyers, sellers, owners, and admins need key pairs to identify themselves to the market.
When you create a new identity, the address that other users will see is usually generated randomly. You can instead import that address as WIF (e.g., from vanitygen).
WIF:
Identity Not Yet Approved
Your identity has not yet been approved by the market admins. You can request this at the following web pages:
The identity appears in your list of keys immediately, but can't be used to send messages on the market until it's approved.
Keys Not Yet Broadcast To Market
The market may not have your latest encryption or Bitcoin escrow release keys. This means that other users might send encrypted messages or funds using older keys that you plan to retire soon.
This loses the benefit of key rotation. To fix this, broadcast your latest public keys now.
Export Cryptographic Keys
You have generated new cryptographic keys, and you haven't yet exported them. The keys are stored in browser local storage, but you should also export them to a file, and save the file on a local encrypted volume.
If you lose your keys, then you will lose your account's reputation from feedback, access to all encrypted messages, and all escrowed funds.
New Buyer Pseudonym
You can create a new buyer pseudonym. This hides the fact that the same person placed multiple orders from the general public. Choose a server from the list below:
It's best to always use the same server if possible, since the admin of that server can learn the link between your pseudonyms.
Address Book
| Address | Nickname |
|---|
Propose Escrow Release
| TXID | vout | Value |
|---|
Propose that all funds above be released to:
| Address: | |
| Transaction Fee: | BTC |
View Transaction As Hex
signed by /3 partiesFeedback Already Exists
You have already left feedback for this user. To leave new feedback, delete the old feedback first.