FAQ2019-11-27T04:48:08+01:00

Häufig gestellte Fragen und Antworten

Vorsicht bei Online-Servicen2019-11-20T19:05:46+01:00

Sie sollten sich vor jedem Service hüten, der entwickelt wurde, um Ihr Geld online zu speichern.
Viele Börsen und Online-Wallets litten in der Vergangenheit unter Sicherheitsverletzungen, und solche Dienstleistungen bieten in der Regel immer noch nicht genügend Versicherung und Sicherheit, um Geld wie eine Bank zu speichern. Es wird empfohlen eine BURST-Wallet zu installieren um Ihr eigens Geld zu verwalten. Benützen Sie Online-Wallets nur von vertrauenswürdingen Seiten.

Kleine Mengen für den täglichen Gebrauch2019-11-20T19:08:15+01:00

Eine Burst Wallet ist wie eine Brieftasche mit Bargeld. Wenn Sie nicht Tausende von Dollar in der Hosentasche haben, sollten Sie das gleiche Verhalten auf Ihre Burst-Wallet anwenden.
Im Allgemeinen ist es eine gute Praxis, nur kleine Mengen an Bursts auf Ihrem Computer, Mobiltelefon oder Server für den täglichen Gebrauch aufzubewahren und den verbleibenden Teil Ihres Geldes in einer sichereren Umgebung aufzubewahren. Erstellen Sie mehrere Burst-Adressen und verteilen Sie die Mittel entsprechend ihrer Verwendung.

Sichern Sie Ihre Wallet2019-11-20T19:11:44+01:00

An einem sicheren Ort aufbewahrt, kann ein Backup Ihrer Wallet Sie vor Computerausfällen und vielen menschlichen Fehlern schützen.
Es kann Ihnen auch ermöglichen, Ihre Wallet wiederherzustellen, nachdem Ihr Handy oder Computer gestohlen wurde, wenn Sie Ihre Wallet verschlüsselt halten.

Sichern Sie Ihre Wallet Passphrase.

Der Schlüssel zur Wiederherstellung Ihrer Wallet für Burst ist Ihre persönliche Passphrase (privater Schlüssel).
Wenn Sie ein Backup der privaten Schlüssel für Ihre Burst-Adressen haben, können Sie mit diesen Schlüsseln jederzeit Ihr Geld zurückerhalten.

Online-Backups verschlüsseln

Das Risiko des Diebstahls einer online gespeicherten Sicherungskopie ist sehr hoch.
Ein mit dem Internet verbundener Computer kann auch von bösartiger Software angegriffen werden.
Es ist daher ratsam, Sicherungskopien zu verschlüsseln, wenn sie über ein Netzwerk zugänglich sind.

Verwenden Sie viele sichere Standorte

Nur ein Standort oder eine Art ist schlecht für die Sicherheit.
Wenn Ihr Backup nicht von einem einzelnen Speicherort abhängt, ist es weniger wahrscheinlich, dass ein negatives Ereignis Sie daran hindert, Ihre Wallet wiederherzustellen. Erwägen Sie die Verwendung verschiedener Medien wie USB-Sticks, Papier und CDs.

Aktualisieren Sie Ihr Backup regelmäßig.

Sie sollten Ihre Sicherungskopien Ihrer Wallet regelmäßig überprüfen.
Stellen Sie sicher, dass es alle kürzlich erstellten Burst-Adressen enthält und dass das Speichergerät noch funktioniert.

Halten Sie Ihre Software auf dem neuesten Stand2019-11-20T19:14:09+01:00

Die Verwendung der neuesten Version Ihrer Burst-Software ermöglicht es Ihnen, wichtige Stabilitäts- und Sicherheitsupdates zu erhalten.
Updates können Probleme mit unterschiedlichem Schwierigkeitsgrad verhindern, neue nützliche Funktionen enthalten und helfen, Ihre Wallet sicher zu halten.
Mit der neuesten Version Ihrer Wallet-Software stellen Sie auch sicher, dass Sie sich mit dem Burst-Netzwerk verbinden können.
Darüber hinaus ist die Installation von Updates für alle anderen Programme auf Ihrem Computer oder Mobiltelefon ebenfalls wichtig, um Ihre Wallet-Umgebung sicherer zu machen.

Denke Sie an Ihr Testament2019-11-20T19:16:50+01:00

Ihrw Burst können für immer verloren gehen, es sei denn, Sie haben einen Backup-Plan für Ihre Altersgenossen und Familie.
Wenn niemand den Standort Ihrer Wallet oder Passwörter kennt, wenn Sie aufgrund eines Unfalls/Krankheit überraschend versterben  oder nicht mehr kommunizieren können, gibt es keine Hoffnung, dass Ihr Geld jemals wieder verwendet wird.

Sich ein wenig Zeit für diese Dinge zu nehmen, kann einen großen Unterschied machen.

Nachrichten versenden2019-11-24T17:14:26+01:00

Select the Messages option from the left-hand menu or click on the messages icon and/or  click on ‘Send Message’.

  • In the Recipient field, enter the Burstcoin address for the message recipient account.
  • In the Message field, you can enter any text with a length of up to 1000 bytes. When sending, you receive a corresponding error message if you enter longer text.
  • You can select the checkbox ‘Encrypt Message’(only receiver can read it ) or send the data unencrypted (everyone can read it).
    The recipient needs his passphrase to read encrypted messages.
  • When you have sent the message it is listed in the unconfirmed transaxtions(mempool).
  • After the network has processed your message (usually after a few minutes and depending on the fee you choosed), it will be transmitted to your receiver.
Nachrichten erhalten2019-11-24T17:14:46+01:00

Select the Messages option from  menu or click on the messages icon and/or  click on ‘Inbox’.

  • Here you can find all the received messages sorted by Burstcoin account.
    Select one of the sending accounts and all of the messages sent from that account will be displayed.
    If the message has been encrypted, you will see a padlock symbol and a prompt to enter your passphrase in order to decrypt the messages.
  • Selecting one of the messages allows you to enter your passphrase or PIN (like for Pheonix)
Voraussetzungen2019-12-01T12:32:45+01:00

Burstcoin node running 24/7 with fully synchronized blockchain.
You find the software here : Burstcoin Reference Software or also on our download section
It is also recommend to setup a testnet node for QA and testing purposes.
All examples in this document use the 6876 testnet port.
The mainnet port is 8123.

Einzahlungen annehmen2019-12-01T12:33:31+01:00

Unlike Bitcoin’s throw away addresses, Burstcoin addresses are somewhat expensive to maintain.
Each address and public key combination are maintained forever in the blockchain, however maintaining a completely empty account is less costly than maintaining an account with non zero balance.

Due to this we do not recommend using a throw away address per deposit.
Instead, we recommend creating at most one deposit address per user or even direct all deposits to the same address and maintain user identity using a message attached to the deposit transaction.

Deposits can be accepted using one of the following approaches:

  1. Message Based Deposits – sent to a single address, the user is identified by an attached message.
  2. Address per User – a new deposit address for each user.

When using both methods, always use a strong passphrase for the deposit account and protect the deposit account with a public key before accepting deposits.

Message-Based Deposits

Each payment transaction can have an attached message, either in plain text or encrypted. This allows you to identify the customer through a customer number or order number mentioned in the message.

Which identifier you will use in the message to connect the payment to a specific user account is up to you and won’t be discussed in this document.

To monitor your account for new incoming payments, the getAccountTransactions API call is used. You can specify the amount of confirmations needed. (10 recommended)

The API call takes the following parameters:

  1. account – deposit account id or in reed solomon format (with BURST prefix).
  2. timestamp – if specified, transactions should be newer than this block timestamp
  3. type – the type of transaction. For payments this should be 0
  4. subtype – the transaction subtype. For payments this should be 0 as wellsdsd
  5. firstIndex – for pagination purposes
  6. lastIndex – for pagination purposes
  7. numberOfConfirmations – ignore transations with less

To monitor a specific account for payment transactions use the following URL:

http://localhost:6876/burst?requestType=getAccountTransactions&account=BURST-5BE2-6SGA-K455-BCCY3&type=0&subtype=0&numberOfConfirmations=10

note; examples use local node and testnet port

 

This is the JSON response (irrelevant fields omitted):

{ „transactions“: [ { „type“: 2, „subtype“: 1, „timestamp“: 132622393, „deadline“: 1440, „senderPublicKey“: „64ecf79e02001408d86a3148192f10abb94a15f1add7fb7e0d581d0efe406306“, „recipient“: „10446462338210047360“, „recipientRS“: „BURST-5BE2-6SGA-K455-BCCY3“, „amountNQT“: „0“, „feeNQT“: „100000000“, „signature“: „1685ba8dc12b71726406693045b4421e42b1fe57cd42428c6b97701271f1980624f8be54d6ca210fd29bb63abe652ae6beff98095e7931a1df2d82dc6c67e7ef“, „signatureHash“: „155df32a81847c00df529c9d09bc5e1f26618036f68554240b94ab99a50932cb“, „fullHash“: „20aa5e79d5a49b5c07d877fcb4bf85cdc2bb058650f9228f66521799be0bc037“, „transaction“: „6673108509650758176“, „attachment“: { „version.AssetTransfer“: 1, „asset“: „3509939581101213262“, „version.Message“: 1, „message“: „Free RAFFLE share“, „messageIsText“: true, „quantityQNT“: „10“ }, „sender“: „13476626730621357107“, „senderRS“: „BURST-JM3M-MHWM-UVQ6-DSN3Q“, „height“: 548306, „version“: 1, „ecBlockId“: „17903993250352434776“, „ecBlockHeight“: 548297, „block“: „13565806093770253653“, „confirmations“: 115271, „blockTimestamp“: 132622449 }, … more transactions … ] }

Loop over this array of transactions and process the transactions one by one. Note that this response includes both incoming and outgoing payment transactions. You should filter out your own (outgoing) payments by looking at the sender or senderRS account address.

The important information of a transaction response is:

  1. senderRS – the sender’s account id
  2. confirmations – the number of confirmations
  3. amountNQT – the amount sent in NQT form (plancks, like SATs in BTC)
  4. attachment.message – optional, an attached plain text message
  5. attachment.encryptedMessage – optional, an attached encrypted message
  6. timestamp – the time the transaction was made, in seconds since the genesis block
  7. blockTimestamp – the time of the block since the genesis block
  8. confirmations – number of confirmations received for the block in which the transaction is included

confirmations

For most transactions, waiting for 10 confirmations should be enough. However, for transactions with large amount, special attention should be given to the transaction timestamp and deadline parameters, since blocks can become orphaned and transactions cancelled as a result in case their deadline has passed.

When genesis time + timestamp + deadline * 60 is bigger than transaction.blockTime + 23 hours,
a transaction can be accepted when the confirmations count reaches 10.

If (genesis time + transaction.timestamp + transaction.deadline * 60) is smaller than (transaction.blockTimestamp + 23 hours), you should wait until the transaction has 720 confirmations before crediting the user’s account. 720 blocks is the maximum depth a blockchain reorganization can go. By waiting that long, you ensure the transaction is always included. Transactions that only required 10 confirmations will be put back in the blockchain automatically due to their longer deadline time.

The default deadline in the client is 24 hours, which means that in 99% of the cases only 10 confirmations will be necessary before crediting the user’s account.
Genesis time for the Burst blockchain is GMT: Monday, 11 August 2014 02:00:00 Unix epoch 1407722400

To identify the user, you must look at the transaction attachment. If a plain text message is included, attachment.message is set and attachment.messageIsText is set to “true” (as string).
If an encrypted message was attached instead, attachment.encryptedMessage should exist instead. This is not just a string, but an object and contains two keys; data and nonce.

decrypt

To decrypt the message use the decryptFrom API.

This API call takes the following parameters:

  1. account – account id that sent you the encrypted message
  2. data – the encrypted message data extracted from transaction.attachment.encryptedMessage.data
  3. nonce – the encrypted message nonce extracted from transaction.attachment.encryptedMessage.nonce
  4. decryptedMessageIsText – set to “true“ if the message you’re trying to decrypt is text
  5. secretPhrase – passphrase of the account that received the encrypted message i.e. the deposit account

Example: to decrypt the message sent by testnet transaction 12700027308938063138 send the following request parameters:

http://localhost:6876/burst?requestType=decryptFrom&secretPhrase=[passphrase_from_account_BURST-EVHD-5FLM-3NMQ-G46NR]&account=BURST-XK4R-7VJU-6EQG-7R335&data=9fd7a70625996990a4cf83bf9b1568830f557136044fb3209dd7343eec2ed96ec312457c4840dabaa8cbd8c1e9b8554b&nonce=650ef2a8641c19b9fd90a9ef22a2d50af90aa3b0de3d7a28b5ff2ad193369e7a&decryptedMessageIsText=true

The response is:

{ „decryptedMessage“: „test message“, „requestProcessingTime“: 2 }

After you have decrypted the message, you can now credit the customer account with the amount specified in transaction.amountNQT.
Note: If you wish you can show pending deposits to the user for transaction which did not yet reach the required number of confirmations.
You could also check for new transactions by specifying the last block’s timestamp+1 as the timestamp parameter:

http://localhost:6876/burst?requestType=getAccountTransactions&account=BURST-XK4R-7VJU-6EQG-7R335&type=0&subtype=0&timestamp=83099831

To get the last block timestamp, you would look at the last processed transaction blockTimestamp, or use the getBlockchainStatus API

Account-Based Deposits

As discussed above, Burst accounts are an expensive resource and should not be treated like disposable Bitcoin addresses.
For account-based deposits, you basically generate a new random passphrase for each user. The passphrase should be very strong and at least 35 characters long.
Once you have this passphrase, you can get the account id and public key via the getAccountId API call.

  1. secretPhrase – account passphrase
  2. publicKey – account public

Note that you only need to specify one of the above parameters, not both. So in our case, you just specify the secretPhrase parameter.

http://localhost:6876/burst?requestType=getAccountId&secretPhrase=1234

The response is:

{ „accountRS“: „BURST-5WUN-YL5V-K29F-F43EJ“, „publicKey“: „fddcda69eeca58e5d783ad1032d080d2758a4e427881b6a4a6fe43d9e7f4ac34“, „requestProcessingTime“: 2, „account“: „15577989544718496596“ }

On your site’s deposit page, you will need to show the account address extracted from the accountRS field i.e. BURST-5WUN-YL5V-K29F-F43EJ.
If the account hasn’t yet had any incoming transactions, you will also need to display the publicKey to the user.
The public key doesn’t have to be displayed any more after it has had it’s first incoming transaction.

When a user sends funds to a new account, it needs to add the public key, so that an announcement of this key can be made.
Once done, this is no longer needed. Accounts without a public key are only protected by the 64 bit account address not by the 256 public key.

Tracking New Account-Based Deposits

To track new deposits, it’s easiest to simply inspect all transactions in a block to see if any of them are to account addresses you generated. An alternative method would be to use the getBlockchainTransactions API detailed in message-based deposits. (This is to be done in a loop)

Use the getBlockchainStatus API to check if there is a new block. This API call has no parameters.

http://localhost:6876/burst?requestType=getBlockchainStatus

The response includes lastBlock (block id) and numberOfBlocks (the height).

If numberOfBlocks is different from the previous execution of this API request, one or more new blocks have been generated. The transactions from the block which now has 10 confirmations have to be fetched. You should save in your database the height of the last block you processed.

Use the getBlock API to get the block at the height of 10 blocks ago (10 confirmations).

Pass it the numberOfBlocks parameter from the getBlockchainStatus API response after subtracting 11 from this value.

  1. height – height of the block, zero-based.
  2. includeTransactions – set to true to return the array of transactions included in the block

For each transaction, see if the recipientRS field corresponds to one of the deposit accounts you generated for your users. If so, this is an incoming payment. Credit the user’s internal balance and send the money to your hot wallet.

Similarly to message based deposits, special attention should be given to the transaction timestamp and deadline parameters.

After all transactions of this block have been checked, see if you’ve processed the previous block before or not. If not, traverse through the previous blocks chain until you reach the last processed block.

Entnahme/ Senden von BURST2019-12-01T12:31:23+01:00

When a user wants to withdraw to a specific account, you ask him for the account id he wants to withdraw to.
When you receive this account id, you must first check if that account has a public key attached to it or not (i.e. if it’s new or not).

To do this, you must use the getAccountPublicKey API. It takes 1 parameter, account.

account – account you want the public key of

http://localhost:6876/burst?requestType=getAccountPublicKey&account=BURST-C6L6-UQ5W-RBJK-AWDSJ

If the account does not have a public key, you will get this error: { "errorCode": 5, "errorDescription": "Unknown account" }
When you get this error, you should also ask the user for his public key or at least display a warning explaining the risk of using an account without a public key.

When you have both the account id and public key, you can verify that they are correct by comparing the given account id with the account id generated by the public key using the getAccountID API call.

  1. secretPhrase – account passphrase
  2. publicKey – account public key

We want to calculate only by publicKey so our request looks like this:

http://localhost:6876/burst?requestType=getAccountId&publicKey=28f56a81e0f8555b07eacffd0e697b21cbbbdf3cf620db14522732b763564f13

You’ll get back a response like this: {"accountRS":"BURST-C6L6-UQ5W-RBJK-AWDSJ","publicKey":"28f56a81e0f8555b07eacffd0e697b21cbbbdf3cf620db14522732b763564f13","requestProcessingTime":0,"account":"9827273118446850628"}

Now compare the response accountRS to the account id the user provided.
If they are equal, you can go ahead and perform the withdrawal.

Sending BURST

Sending BURST is done via the sendMoney API call. The relevant parameters are:

  1. recipient – recipient’s account address
  2. amountNQT – amount of BURST (in NQT)
  3. feeNQT – transaction fee for the transaction in NQT.
  4. secretPhrase – sender’s account passphrase
  5. deadline – deadline for the transaction in minutes. Should be set to the maximum value of 1440
  6. recipientPublicKey – recipient public key as provided by the user, only needed if the user account has no public key yet (on first transaction)

At the moment (v1.9.2) the recipientPublicKey is optional, however not specifying it, puts the user’s funds at risk. The recipientPublicKey is mandatory in case you like to attach an encrypted message to the withdrawal transaction of a new account.

This request has to be sent using HTTP POST.

The response should look like this if everything went OK: { "fullHash": “10788f7ad3f145b5209da6145327d7fed869…”, ... a lot more information ... }
A correctly executed response should always contain the „transaction“ field which represents the newly created transaction id.
If there’s an error, you may get a response such as this (other errors may apply):{ "errorCode": 5, "errorDescription": "Unknown account" }

Adding a Message To a (Payment) Transaction

You can add messages to any kind of transaction.

To do so, specify the below parameters in your request:

  1. message – plain text message.
  2. messageIsText – should be set to the string “true” if text.
  3. messageToEncrypt – plain text message that should be encrypted.
  4. messageToEncryptIsText – should be set to the string „true“ if text.

In case you want to attach a plain text message, specify message and set messageIsText to “true”.

encrypt

If you want to attach an encrypted message that can only be read by the recipient, specify messageToEncrypt and set messageToEncryptIsText to “true”.
To create the messge you may use the encryptTo API call.

Note that these messages are not mutually exclusive, you can add both a plain text and encrypted message in the same transaction.
Allowing the user to add a message on your withdrawal page is recommended, so that you can coordinate with other services who use a message-based deposit system.

Hot and Cold Wallets

You should not keep all of your user’s deposits in a single hot wallet.
A hot wallet is a wallet for which the passphrase is stored somewhere on your server, so that you can send money from it.

Instead, you should have both a hot and cold wallet. The cold wallet should hold most of the coins and not be accessible from any of your servers. Ideally, you’d manually send from your cold wallet to your hot wallet when more coins are needed for day-to-day operations.

So the best thing to do is to have money sent to your cold wallet address, and then send out to your hot wallet manually when needed.

Zusätzliche Informationen2019-12-01T12:34:16+01:00

Burst Account Format

The account ID is stored internally as a 64 bit signed long variable. When used in APIs it is usually returned as both unsigned number represented as string and using alphanumeric Reed-Solomon representation starting with „BURST-“ prefix.

For example: BURST-ER8M-SYV3-R7EK-EUF3L

In API request parameters and response JSON, you will find both representations, the numeric representation is typically displayed as account, sender, recipient.
The alphanumeric representation is typically displayed as accountRS, senderRS, recipientRS (simply always add “RS”). RS stands for Reed-Solomon.
This form of address improves reliability by introducing redundancy that can detect and correct errors when entering and using account ID’s.

Burst and NQT Amounts

All amounts should be converted to NQT format to be used in API calls.
NQT is the name given to 0.00000001 Burst (or 10^(-8) in mathematical shorthand).
The NQT to Burst ratio is equivalent to the Satoshi to Bitcoin ratio.
Simply put, 1 Burst is 100000000 NQT, therefore to convert Burst to NQT, simply multiply by 100000000.

Token(Asset) and currency QNT amounts

Each Token and Currency (generally referred to as „Holding“) has specific number of decimal positions to which this holding is divisible.
API requests and responses always expect the holding quantity to be specified as a whole number without decimal positions.
We refer to this value as QNT.
For example, when transferring 12.34 units of holding XYZ which has 4 decimal positions, specify the QNT value as 123400.

Minimum Fee

All outgoing transactions require a fee of at least 735000 NQT at the moment.
The minimum value is 735000 NQT. use suggestFee API call. for cheap/standard/priority suggestions.

Ausagbe von Token2019-11-24T16:45:25+01:00

Within the wallet (BRS) from Burstcoin your are empowered to issue Token as you wish.
ERC20 is a popular Ethereum standard for token management and the BURST Token already supports most of the ERC20 operations out of the box without the need to issue a smart contract.

The following attributes need to be set to create a Token :

  • ASSET NAME
    The name of the asset you intend to issue. This is also the name announced to other traders, allowing them to find this asset.
    Mandatory: you cannot issue an unnamed asset. Names are non-unique: multiple assets can be issued with the same name.
    Note: for this reason, it is important to pay close when buying or selling!
    Length: between 3 and 10 characters.
    Characters allowed: uppercase letters, lowercase letters, and numbers.
  • DESCRIPTION
    In this field, you can briefly describe the asset being issued.
    Mandatory: this field is mandatory.
    Characters allowed: it can contain any Unicode characters but should be URL-encoded. Maximum length of 1,000 characters.
  • QUANTITY
    Specify how many tokens you intend to create.
    Mandatory: this field is mandatory. Must be a whole number
  • DECIMALS
    This field defines the divisibility of the token.
    As an example, by defining 2 decimals, the minimum amount of tokens you can sell or buy is 0.01.
    Mandatory: this field is mandatory.
    Limits:  0 to 8 decimals. The latter corresponds to the minimum of 0.00000001 tokens.
  • FEE
    Define the fee related to issuing the asset.
    1,000 BURST is the minimum required to issue an asset (to avoid spam assets).
    Mandatory: this field is mandatory.

 

 

Übertragen von Token2019-11-24T16:45:54+01:00

Any balance of Token on your BURST account can be transfered to another BURST account by a minimum fee of 0,00735 BURST.
Tge follwoing attributes need to be set to be able to transfer your Token size :

  • BURST Recipient adress
    Specifiy the receiver of your Tokens
    Mandatory: this field is mandatory. Must be a valid BURST adress.
  • Quantiy
    Specify how many tokens you intend to transfer.
    Mandatory: this field is mandatory. Must be a number plus max digits allowed for this Token
  • Message
    You can set a message to the receiver if you like.
    Optional: Message can be filled or kept empty

 

Wallet Schnittstelle2019-11-24T16:51:04+01:00

The Token exchange is accessible within the Burstcoin wallet.  If your wallet was installed using QBundle you need only to start the wallet and connect to your Burstcoin account.
If you are using a standalone wallet (currently all wallets installed without using QBundle), the exchange is accessed using a standard web browser to connect to your localhost (wallet).
To connect, enter  127.0.0.1:8125   into the address bar.

At the moment a Token is named Asset on the BRS wallet.

Select asset exchange  to observe an asset, select add asset and enter the asset id or the issuing account id.
Your selections will be listed along with information such as a description, buy and sell orders, quantity, etc.

You can check the transfer history of assets in your possession which are found under my Assets.
This includes assets that you have purchases as well as any assets that you have issued.

You can check that status of open order by selecting open orders.
From this list you can cancel any order.
Order cancellations are not instantaneous as the order cancellations must be propagated through the network.
There is a possibility that your order may fill while this process is proceeding.

To issue an Token , select issue asset.
The form for entering the asset information will appear.

There are several mechanisms for paying and rewarding your investor.
To do so, you will use one of three Token distribution modules:  dividendsautomatic asset distribution, or share swap.
Select payout dividends to choose one of the three modules.

By default, the asset exchange does not list any asset.
You must locate the assets that you wish to follow and add them to your list using the add asset button.
There are several online resources (asset exchange explorers) being developed to help rank assets in meaningful ways, such as by volume, number of trades, or another useful metric.
These resources include a variety of filters to help you locate assets of interest.
After locating an asset, you can bookmark it your list.

Note: Incognito mode (or its equivalent) is not supported for adding assets to your watch list.  In order for your list to retain the asset that you add to it, your browser must be in normal mode.

By selecting an asset, the interface area will automatically display the corresponding information.
This includes the number of tokens that have been created (“quantity”), how divisible is the token (“asset decimals”), a brief description of the asset, who created the asset (“account”) and the asset identifier (“asset ID”). This information is critical, in fact the asset names are non-unique.
This means that there can be multiple assets that have the same name.

 

Kauf/Verkauf von Token2019-11-24T16:51:19+01:00

You need to perfom the follwoing action to buy or sell a Token(Asset):

  • Select the Token from the list.
  • Click on “Buy *Token Name* with BURST
  • Quantity: define the number of assets that you are interested in buying.
  • Price: set the amount you are willing to pay.  Warning: “price” refers to the cost of a unit of tokens. So, by entering 10, you are willing to pay 10 BURST per token.
  • Fee: define the fee (the minimum fee is .00735 BURST).
  • Select buy or sell
Kauf/Verkauf-Auftrag löschen2019-11-24T16:51:50+01:00

You can cancel an order at any time.  However,

  • The process is not instantaneous.  Your order may be accepted before your cancellation reaches the network.
  • Cancellation orders incur a minimum transaction fee.
  • An order that is in the process of being canceled will appear in red in the ‘Open Orders’ menu.
Martkplatz Einführung2019-11-23T06:59:07+01:00

Marktplatz – die Zukunft des P2P-Handels.

Der Burst-Marketplaz bietet ein Protokoll für dezentrales P2P-Verkäufe an. Es ist nicht mehr notwendig, sich auf etablierte Marktseiten anzubinden, die Provisionen dafür erheben um Ihnen die Verkaufsprozesse zu erleichtern, dies übernimmt absofort das Burst-P2P-Protokoll. Jede Art von Ware kann gekauft und verkauft werden. Der Marktplatz eignet sich besonders für digitale Güter wie Software, Musik und Videos. Käufer geben die Burst-Adresse des Verkäufers ein und können desen Artikel gegen BURSTs kaufen. Die Käufer erhalten dann Anweisungen zum Empfangen oder Herunterladen ihrer gekauften Produkte – keine Zwischenhändler, keine Gebühren und keine Verzögerungen. Alle Transaktionen zwischen Käufer und Verkäufer werden direkt auf der Burst-Blockchain abgewickelt.

Der Marktplatz wird von der BRS-Wallet unterstützt.
Wenn die Wallet läuft, können Sie auf die lokale  allet zugreifen, indem Sie http://localhost:8125/ eingeben.
In der Seitenleiste finden Sie Menüs für den Marktplatz und den Shop.
Sie finden die folgenden Aktionspunkte:

  • Marktplatz durchsuchen
    Geben Sie die Adresse eines Verkäufers ein, um dessen Produkte zu sehen.s.
  • Gekaufte Produkte
    Sehen Sie alle Ihre bisherigen Einkäufe.
  • Meine Produkte zum Verkauf
    Sehen Sie sich Ihre Verkaufsartikel an und aktualisieren Sie Ihre Angebote.
  • Meine ausstehenden Bestellungen
    Hier sehen Sie ausstehende Bestellungen von Benutzern, die ein Produkt kaufen möchten.
  • Meine ausgeführten Bestellungen
    Zeigt alle abgeschlossenen Bestellungen und das Feedback Ihrer Kunden an.
  • Produkt zum Verkauf anbieten
    Hier fügen Sie ein neues digitales Produkt auf dem Marktplatz hinzu.

 

Wie man ein Produkt auf dem Marktplatz kauft2019-11-23T07:00:35+01:00
  • Öffnen Sie Ihre Burstcoin-Wallet und wählen Sie Marktplatz aus.
  • Wählen Sie Marktplatz aus dem Menü und dann Marktplatz suchen.
  • Geben Sie die Burstcoin-Adresse eines Verkäufers ein, um eine Liste der Artikel zu sehen, die er zum Verkauf anbietet.
  • Klicken Sie auf den Namen eines Produkts, um einen Kaufdialog zu öffnen.
    Geben Sie Menge und Liefertermin (in Stunden) ein.
    Der Liefertermin definiert die Zeit, die Sie bereit sind, darauf zu warten, dass der Verkäufer liefert, bevor die Transaktion storniert wird.
    Überprüfen Sie Ihre Daten und klicken Sie auf Kaufen.
  • Erfolgreich erteilte Bestellungen erscheinen im Menü der gekauften Produkte mit einem anfänglichen Bestellstatus von „Ausstehend“.
    Nach der Bestätigung des Netzwerks (Blockgenerierung) ändert sich der Auftragsstatus in „In Bearbeitung“.
    Wenn das Produkt geliefert wurde, ändert sich der Status auf „Abgeschlossen“.
  • Klicken Sie auf den Namen, um den Dialog zu öffnen.
    Geben Sie Ihre Passwort ein, um die Nachricht des Verkäufers zu entschlüsseln.
    Hier finden Sie Informationen darüber, wie Sie Ihr Produkt erhalten können.
    Sie haben nun die Möglichkeit, dem Verkäufer ein Feedback zu geben.
Wie man ein Produkt auf dem Marktplatz verkauft2019-11-23T06:59:22+01:00
  • Öffnen Sie Ihre Burstcoin Walet und wählen Sie Meinen Shop aus.
  • Klicken Sie oben rechts oben auf die Liste der zu verkaufenden Produkte.
    Beschreiben Sie Ihr Produkt.

    • Name: Der Name des Produkts.
    • Beschreibung: Mehr Details zum Produkt.
      Sie können einen Link zu unserer Werbe-Website hinzufügen, wo Sie das Produkt ausführlich präsentieren können.
    • Tags: (optional) – Geben Sie bis zu drei Tags ein, die durch Kommas getrennt sind.
    • Preis: Der Produktpreis pro Einheit in Burstcoin.
    • Menge: Die Anzahl der Artikel, die Sie auf Lager haben.
      Dies wird bei jedem Verkauf automatisch verringert.
  • Bestätigen Sie das Angebot, indem Sie auf Zum Verkauf stellen klicken.
    Es wird dann kursiv unter meinen zu verkaufenden Produkten aufgeführt.
    Nachdem Ihr Angebot in einem Block, in der Regel nach wenigen Minuten, bestätigt wurde, wird es in normaler Schrift als Link aufgeführt.
  • Wenn jemand eine Bestellung aufgibt, um Waren von dir zu kaufen, wird sie in meinen ausstehenden Bestellungen angezeigt.
  • Um den Verkauf abzuschließen, drücken Sie die Schaltfläche Waren liefern.
    Geben Sie im Popup-Fenster Ihre Password ein, um die Nachricht des Käufers zu entschlüsseln.
  • ErfasssenSie die Käuferinstruktionen, wie der Käufer die Ware herunterladen oder erhalten kann.
    Sie können Ihrem Käufer optional einen Rabatt gewähren.
    Geben Sie Ihre Password ein und wählen Sie Kauf liefern, um den Kauf abzuschließen.
  • Der abgeschlossene Prozess erscheint in meinen abgeschlossenen Aufträgen.
  • Für Details klicken Sie auf den Produktnamen.
    Wenn der Käufer ein Feedback gegeben hat, finden Sie es hier.
    In diesem Abschnitt können Sie auch eine Rückerstattung vornehmen, falls nötig.
Produkte verwalten2019-11-23T06:59:30+01:00
  • Öffnen Sie Ihre Burstcoin Wallet und wählen Sie Mein Shop aus.
  • Klicken Sie auf Mein Shop und hier auf Meine Produkte zum Verkauf.
  • Sie sehen eine Liste aller Ihrer gelisteten Produkte mit 3 Aktionstasten:
    • Preis ändern
      Sie können für zukünftige Verkäufe Ihren Preis für das Produkt ändern.
      Bereits verarbeitete Verkäufe sind von dieser Änderung nicht betroffen.
    • Menge ändern
      Sie können die Menge der Produkte, die Sie verkaufen möchten, ändern.
    • Löschen
      Sie können das zum Verkauf stehende Produkt jederzeit wieder löschen.
Alias Einführung2019-11-23T07:12:22+01:00

Das Burstcoin-Alias-System ist ein Funktion, das die Grundlage für jedes System bilden kann, das die Zuordnung oder Übersetzung von alphanumerischem Text in eine beliebige Folge von lateinischen Zeichenzahlen und Buchstaben erfordert. So kann es beispielsweise als Grundlage für ein dezentrales DNS-System, eine Online-Shopping-Cart-Anwendung usw. verwendet werden. Es ermöglicht im Wesentlichen, dass ein Text durch einen anderen ersetzt wird, so dass Schlüsselwörter oder Passphrasen verwendet werden können, um andere Dinge darzustellen – Namen, Telefonnummern, Adressen, Websites, Kontonummern, E-Mails, Produkt-Codes, etc. Eine einfache Anwendung wäre die Erstellung von leicht zu merkenden Aliasen für Burstcoin-Kontonummern.

Es gibt 2 Möglichkeiten, Burstcoin-Aliase zu verwenden, ohne sich auf Plugins von Drittanbietern für Ihren Browser zu verlassen:

  • Server-side
    Ein Webserver analysiert die Burstcoin-Blockchain und ersetzt „Burst-Links“ durch entsprechende Adressen, bevor er HTML-Dokumente an Benutzer sendet.
  • Client-side
    Ein Webbrowser führt JavaScript-Code aus, der sich mit den Burst-Wallet verbindet und „Burst-Links“ durch deren Adressen ersetzt. Dazu muss ein kleines Skript eingebettet werden. Das Skript wird CORS, JSON und andere Techniken verwenden.
Alias Prozesse2019-11-23T07:14:38+01:00

Alias anlegen

  • To create an alias, send a transaction that states “This Text = That Text”.   Use the ‘Aliases’ menu and click ‘Register Alias’.
  • To change an alias, send another transaction with a new definition.
    Use the ‘Aliases’ menu and click ‘Edit’.
    Only the account that created an alias can change it.

Alias regestrieren

  • Click on ‘Register Alias’ in the upper right corner.
  • Select the ‘Type’: “URI”, “Account” or “Other”.
  • In the ‘Alias’ field, enter the name without blank spaces.
  • Depending on the selected ‘Type’, the text input field is named ‘URI’, ‘Account ID’ or ‘Data’.
    The ‘Data’ field can contain any text.  The maximum length is 1,000 bytes.
  • After the network has processed your message your Alias is reachable.

Alias anpassen

  • Click on ‘Edit’ behind the alias you want to change.
  • You can modify the ‘Type’ and ‘Data’, but you can not rename the ‘Alias’.
  • Click ‘Update’.

Alias übertragen

An alias can be transferred for the minimum Burstcoin fee.(0,00735 BURST)

  • Click on the ‘Transfer’ button behind the alias to be transferred.
  • Enter the ‘Recipient’ account id and a message (optional).
  • Enter your ‘Passphrase’ and click ‘Transfer Alias’.

Alias verkaufen

Aliases can be sold to specific Burstcoin accounts or to the general public.
When selling aliases, the prices can be set individually.

  • Click on ‘Sell’ behind the alias to be sold.
  • You can sell it to a specific user or offer it on the Burstcoin network.
  • Enter the price and the corresponding data.
  • Confirm and  click on ‘Sell Alias’.
Einführung2019-12-01T12:54:31+01:00

Der Begriff Plotten ist ein Name für die Bereitstellung von Speicherplatz für Berechnungen im Burstcoin-Netzwerk. Ein Plot ist eine Datei mit vorberechneten Hashes, die verwendet werden kann, um Blöcke für Burstcoin Blockchain zu erstellen. Die Plot-Files  werden später von der Mining-Software genutzt und können als die Hash-Rate des  Miners angesehen werden.

Algorithmen und Akronyme2019-12-01T16:21:48+01:00

Before we dive deep into how plotting works we need to get familiar with all different terms used in the procedure.

Shabal

Shabal is the name of the crypto/hash function used in Burstcoin. Shabal is a rather heavy and slow crypto in relation to many other like i.e. SHA256. Because of this it makes it a good crypto for Proof of capacity coins like Burstcoin. This is because we store the precomputed hashes while it is still fast enough to do smaller live verifications. Burst uses the 256bit version of Shabal also known as Shabal256.

Hash / Digest

A hash or digest in this context is a 32Byte (256bit) long result of the Shabal256 Crypto.

Nonce

When generating a plot file, you generate something that is called nonces. Each nonce contains 256Kilobyte of data that can be used by miners to calculate Deadlines. Each nonce will have its own individual number. This number can range between 0-18446744073709551615. the number is also used as a seed when creating the nonce. Because of this each nonce has its own unique set of data. One plot file can contain many nonces.

Scoop

Each nonce is sorted into 4096 different places of data. These places are called scoop numbers. Each scoop contains 64byte of data which holds 2 hashes. Each of these hashes are xored with a final hash (we get to final hash in generating a nonce chapter).

Account ID

When you create your plot file it will be bound to a specific Burst account. The numeric account ID is used when you create your nonces. Because of this all miners have different plot files even if they use the same nonce numbers.

Generierung Nonce(s)2019-12-01T16:23:02+01:00

The first step in creating a nonce is to make the first seed. The seed is a 16byte long value containing the account id that we will be generating a nonce for and the nonce number. When this is done we start to feed the Shabal256 function to get our first hash.

We have produced the first hash. This is the last hash in the nonce. Hash #8191. Now we take this produced hash (#8191) and pre-append it to the starting seed. The result will now be our new seed for the next round of shabal256 computation.

We now have produced two hashes. Hash #8191 and Hash #8190. This time we pre-append Hash 8190 to the last seed we used. The result will now be a new seed to feed Shabal256.

Once again, we have created a new hash. This procedure of pre-appending resulting hashes to a new seed will continue for all 8192 hashes we create for a nonce. After iteration 128 we have reached more than 4096 bytes in the seed. For all remaining iterations we will only read the last 4096 generated bytes.

Once we have created 8192 hashes we are now going to make a Final hash. This is done by using all 8192 hashes and the first 16bytes as seed.

The final hash will now be used to xor all other hashes individually.

We have now created our nonce and can store it in a plot file before we continue to the next nonce.

POC2 Format2019-12-01T16:23:34+01:00

The POC2 nonce format is created the same way as when we create POC1 with a slight addition to the end of the process. To create a POC2 formatted nonce we need to shuffle the data around. If we divide the nonce in 2 halves we get a range with scoops 0-2047 and 2048-4095. Let’s call 0-2047 the low scoop range and 2048-4095 the high scoop range. To shuffle the data into correct place we take the second hash from a scoop in the low range and swap it with the second hash in its mirror scoop found in the high range. The mirror scoop is calculated like this:

MirrorScoop = 4095 – CurrentScoop

 

Plot Struktur2019-12-01T16:24:05+01:00

When we are mining we read from one or more plot files. The miner software will open a plot file and seek the scoop locations to read the scoops data. If the plot file is unoptimized the scoop locations will be on more than one place. In the following example the miner will be seeking and reading scoop #403.

This is not the most effective way since the miner will spend a lot of time to seek new locations on the storage device to be able to read the scoops. To prevent this, we can optimize plots or use plotter software that creates optimized plots from the beginning. Optimization is done by reordering the data in the plot file and grouping all data from the same scoop number together.

Basically, what we have done is to divide the plot file into 4096 portions where we split up all the nonces data based on scoop numbers. When the miner now wants to read Scoop 4096 it only seeks one time and read all data sequentially. This provides better performance.

 

Gruppierungen und Dateinamen2019-12-01T16:24:52+01:00

Stagger

A stagger is basically a group of nonces in a plot file. The groups in the plot file is written in an optimized way. A given stagger number tells you how many nonces there are in each group. To find out how many groups there are in a plot file you take the number of nonces and divide it with the stagger number. If the stagger number is equal to the number of nonces in the file, there is only one group and the plot file is completely optimized. If this is the case the miner will not care about the stagger. If for some reason your division ends up with decimals, your plot file can be assumed broken. Poc2 formatted plot files cannot have staggers. They are always written in an optimized way.

Filenames

Since a plot file only contains raw data there is no headers in the files. All information needed for a user and miner is set in the filenames.
The formatting of the filename is as follows:

POC1 format: AccountID_StartingNonce_NrOfNonces_Stagger

POC2 format: AccountID_StartingNonce_NrOfNonces

 

Einstellung2019-12-01T16:25:37+01:00

Reward assignment is a transaction that notifies the network which account is to be credited for block rewards and transaction fees attributable to an individual miner’s account. It is a prerequisite for both solo and pool mining!

For solo burstcoin mining, the reward assignment transaction specifies the solo miner’s account.  For burstcoin pool mining, the transaction specifies the mining pool operator’s account. In the context of pool mining, the reward assignment transaction delegates authority to the pool to uses the participating miner’s submitted deadlines and to sign newly forged blocks using the participating miner’s account.  Note:  forged blocks are always signed by the account belonging to the miner who submitted the deadline used to forge the block.

To perform the reward assignment transaction, consult the documentation for the specific wallet being used.  The procedure generally follows this form:  Select tools – enter reward recipient address in Reed-Solomon format – select “Set Reward Recipient”.  Most wallets include a list of pool operations.  Selecting from this list will generally configure the wallet automatically.  Lists are updated frequently, but newer operations may not yet be included.  In this case, information specific to the chosen pool operation will have to be added manually.

Einführung2019-12-01T16:26:17+01:00

With most cryptocurrencies that are not based on Proof-of-Stake, there is a process called mining. This process is the foundation for a blockchain to grow and secure transactions within the network. Burstcoin is no different, except that you use precomputed hashes to find values that can be used to forge a block. To fully understand this document, you should read the document named technical information to create plot files. This document is intended to be an overview of the processes. It is technical information, but not deep enough to be used as a reference for a programmer since information regarding subjects like AT, subscriptions, and assets is missing.

Algorithmen und Akronyme2019-12-01T16:27:07+01:00

Shabal / Sha256 / Curve25519

Shabal, Sha256 and Curve25519 are cryptographic hash functions used in this text. Shabal is the main one used by Burstcoin. Shabal is a rather heavy and slow cryptographic hash function in relation to many others like SHA256. Because of this, it makes it a good crypto for Proof-of-Capacity coins like Burstcoin. This is because we store the precomputed hashes, and it is still fast enough to do smaller live verifications. Burst uses the 256bit version of Shabal also known as Shabal256.

Hash / Digest

A hash, or digest in this context, is a result when computing data through a cryptographic hash function. If not said otherwise, the length of a hash is 32Bytes (256bit).

Plot files

When mining, you read precomputed hashes from files stored on a storage device. These files are called plot files.

Nonce

Within a plot file, there are one or more groups of data called nonces. One nonce contains 8192 hashes, and because of that, the nonces are 256KiB large. Each nonce has its own individual number. This 64bit number can range between 0-18446744073709551615 (264).

Scoop

Each nonce is sorted into 4096 different places of data. These places are called scoop numbers. Each scoop contains 2 hashes. Each of these hashes are xored with a final hash.

Account ID

When you create your plot file it will be bound to a specific Burst account. Because of this, all miners have different plot files.

Deadline

When you mine and process your plot files, you will end up with resulting values called deadlines. The values represent the number of seconds that must elapse since last block was forged before you are allowed to forge a block. If no one else has forged a block within this time, you can forge a block and claim a block reward.

Block reward

If you are lucky enough to forge a block, you will get Burstcoin as a reward. This is called a block reward. The block reward decreases 5% every 10800 blocks. This is roughly every 30 days since each block is supposed to be forged every 4 minutes (360 blocks a day).

Base target

Base target is calculated from the last 24 blocks. This value adjusts the difficulty for the miners. The lower the base target, the harder it is for a miner to find a low deadline. It gets adjusted in a way that Burstcoin can have an average of 4 minutes for each block.

Network Difficulty

Network Difficulty, or NetDiff in short, is a value that can be read as an estimate on the total amount of space in terabytes dedicated to mine Burstcoin. Since this is a value that changes with every block in relation to base target, it should be taken into an average of at least 360 values before considered to be somewhat accurate.

Block Height

Every block forged gets an individual number. Every new block forged gets the previous block’s number + 1. This number is called block height, and can be used to identify a specific block.

Block Generator

When a block is forged, an account has found a nonce and a deadline. Block generator is the account used when forging a block. This is the account from which a deadline has been found when forging a block. This is always the real account even if a reward assignment has been set.

Generation Signature

Generation signature is a based from the previous block generation signature and block generator. This value is then used by miners to forge a new block. Generation signature is 32bytes long.

Block signature

Every block is signed by the generator who forges a block. This is done by taking most parts of the block and signing it with the block generator’s private key using both Sha256 and Curve25519. The result is a 64byte long hash.

Reward Assignment

Reward assignment is frequently used when pool mining.  When changing your reward assignment, you tell the network that another account (the pool account) is acting in your place for 2 specific features. The first feature is that all block rewards that should be given to your account will now be given to the pool account instead. Secondly, for the pool to be able to utilize the deadlines found from your plot files, it is also granted the action to sign the newly forged blocks with the account belonging to the pool.

Der Prozess des Minen2019-12-01T16:27:44+01:00

All references to wallet in this text can also be a pool depending on scenario.
All references to miner in this text is a software able to do a mining operation for Burstcoin.

The first thing that happens when you start mining, is that the miner talks to the wallet and asks for mining information. This information contains a new generation signature, base target, and the next block height. Before the wallet sends over this info, it creates the generation signature by taking the previous generation signature together with previous block generator and runs this though shabal256 to get the new hash. The miner will now take the new 32byte generation signature, and the 8byte block height, and put them together as a seed for Shabal256. The result will be a hash value called Generation hash.

Now, the miner will do a small mathematical operation on this hash to find out which scoop number to use when processing the plot files. This is done by taking the generation hash modulo 4096, as there are only that many scoops.

Next step for the miner is to read all the 64-byte long scoops from all nonces in all plot files. It will process them individually through shabal256 together with the new generation signature to get a new hash called target. This target is now divided with base target and the first 8bytes of the result is the value deadline.

To prevent so-called “nonce spamming” to the wallet, the miner usually checks if the current deadline found is lower than the lowest one it has found so far. Usually there is also a max value that can be set, as ridiculously large deadlines are of no use to anyone. After these checks, the miner submits information to the wallet. This information contains the numeric account ID bound to the plot file, and the nonce number that contains the scoop data used to generate the deadline. If you are solo mining the miner also sends over the passphrase for the account id used in plot files. If the password is not sent when solo mining, the wallet would be unable to forge blocks for that account. When pool mining, the passphrase for the pool account id is used.

 

Block Erstellungsrozess2019-12-01T16:28:30+01:00

Handling deadlines

The wallet has now received the information submitted by the miner, and will now create the nonce to be able to find and verify the deadline for itself. After this is done, the wallet will now check and see if an equal amount or more seconds has passed as defined by the deadline. If not, the wallet will wait until it has. If a valid forged block from another wallet is announced on the network before the deadline has passed, the wallet will discard the mining info submitted since it is no longer valid. If the miner submits new information, the wallet will create that nonce and check if the deadline value is lower than the previous value. If the new deadline is lower, the wallet will use that value instead. When the deadline is valid, the wallet will now start to forge a block.

Forging

There are two limits for a block. First, a block can contain max. 255 transactions. The second is that a block payload can have max. 44880bytes (43KiB).  The wallet will start by getting all of the unconfirmed transactions it has received from users or from the network. It will try to fit as many of these transactions possible until it hits one of the limits, or until all transactions are processed. For each transaction the wallet reads, it will do checks. For example,  if the transaction has a valid signature, if it has a correct timestamp, etc. The wallet will also sum up all of the added transactions amounts and fees. The block itself will only contain the Transaction ID of each transaction and one Sha256 hash of all the transactions included. Complete transactions are stored separately. Beside this, a block contains many different sets of values.

Inhalt eines Blocks2019-12-01T16:29:02+01:00

Block version number

The version number is basically telling the wallet what a block can contain and how it is contained. This number changes each time a block gets a new format.

List of Transaction ID

A List of all transaction IDs that are included in this block

Payload Hash

This is the Sha256 hash of all the data in the payload of the block

Timestamp

A timestamp that will describe when the block was forged; derived from the birth of the blockchain. Birth date: 11 August 2014, Time: 02:00:00

Total amount of coins

This is the sum of all transactions in the block

Total amount of fees

This is the amount of fees that will be given to the block forger for generating this block.

The length of the payload

This is a number in bytes representing the length of the payload.

Public Key

This is a public key for the account that forges the block.

Generation Signature

The 32byte generation signature that was used to forge the block.

Previous block hash

A Sha256 hash of the contents from the previous block.

Previous block ID

This is the first 8 bytes in the previous block hash converted to a number.

Cumulative Difficulty

Used to prevent Nothing at Stake problems during potential forks. Calculated: Previous Cumulative Difficulty + (18446744073709551616 / base target)

Base Target

The base target used when forging this block

Height

This block’s height value

Block ID

This is the first 8 bytes in block’s hash converted to a number

Nonce

The nonce number used to forge this block.

AT

If an AT is added to this block, this is the payload bytes for that AT.

Block Signature

This is a 64byte hash generated with the forger’s private key and block contents. When this is done, it will be announced to the network. The wallet will connect to all peers and send the block over to them. The peer will receive the block and verify that all information is not spoofed.

ENGRAVER2019-12-01T16:29:38+01:00

Status :Stable
Format : POC 1, POC 2
Engraver is a BURST plotter that natively generates optimized plot files.
It generates PoC2 files and is intended to work on any UNIX system with a sufficiently sane filesystem (able to pre-allocate space), but for now only Linux and MacOS have been tested.
64bit only!

Main Developer: PoC-Consortium
Download link: https://github.com/PoC-Consortium/engraver

TurboPlotter 90002019-12-01T16:30:07+01:00

Satus :Stable
Format : POC 1, POC 2
TurboPlotter 9000 is a CPU/GPU PoC 1 + PoC 2 plotter and plot integrity checker.

Main Developer: Blackpawn
Download link: https://blackpawn.com/tp/
Platform: Windows, Linux, MacOS

XPlotterGui2019-12-01T16:31:10+01:00

Status :Stable
Format : POC1, POC 2
XplotterGui is a GUI version of Xplotter with SSD Cache, File Merging, and POC2 Conversion features.

Main Developer: JohnnyFFM
Download link: https://github.com/JohnnyFFM/XPlotterGui/releases/latest
Platform: Windows

XPlotter modifiziert2019-12-01T16:31:48+01:00

Status :Stable
Format : POC1, POC 2
XPlotter is the default plotter that comes with QBundle and provides CPU PoC 1 plotting with AVX support. This modified version supports PoC 2 plotting.

Main Developer: JohnnyFFM
Download link: https://github.com/JohnnyFFM/XPlotter/releases/tag/v.1.31
Platform: Windows

gpuPlotGenerator (veraltet)2019-12-01T16:32:19+01:00

Satus : Stable, Outdated
Format  POC1

Main Developer: bhamon
Download link: https://github.com/bhamon/gpuPlotGenerator/releases/tag/v4.2.2
Platform: Windows, Linux, MacOS

Scavenger2019-12-01T16:32:56+01:00

Scavenger is a burst miner written in Rust.
It offers:

  • SSE2, AVX, AVX2, AVX512F and NEON support
  • OpenCL GPU support
  • DirectIO

Main Developer: PoC Consortium
Download link: https://github.com/PoC-Consortium/scavenger/releases
Platform: Windows, MacOS, Linux, Unix
(32 & 64 bit)

Blagominer2019-12-01T16:33:29+01:00

This softwate features:

  • update with Collision free dual mining
  • Tracking (and displaying) of possibly corrupted plot files

Main Developer: andzno1
Download link: https://github.com/andzno1/blagominer/releases

Burstcoin-jminer2019-12-01T16:33:56+01:00

Burstcoin-jminer is a GPU assisted Proof of Capacity (PoC) Miner for Burst.

Main Developer: de-luxe
Download link: https://github.com/de-luxe/burstcoin-jminer/releases/tag/0.5.2-RELEASE

Platform: Windows, Linux, MacOS

CreepMiner2019-12-01T16:34:25+01:00

CreepMiner is a client application for mining Burst on a pool or solo.
It supports CPU mining (SSE2/SSE4/AVX/AVX2) or GPU mining (OpenCL, CUDA).

Main Developer: Creepsky
Download link: https://github.com/Creepsky/creepMiner/releases
Platform: Windows, MacOS, Linux x86_64 or ARM7

Burstcoin Pool2019-12-01T16:34:58+01:00

A free of licence Burstcoin Poolsoftware created by BAT Developer Harry.
This pool-software can be downloaded from the burst-app-team-github.

The software is working with Java 8 and has an UI which is clear and well-arranged.

Pool Übersicht2019-12-01T16:35:29+01:00

If you like to join a pool you can get a good overview on this page : https://explorer.burstcoin.network/?action=network_chart

If you want to help the BMF team and its activities, we recommend that you join one of the two pools of them.
The fees that the pools receive go directly back to the BMF Marketing Burst account and are only used for BURST Marketing, Bounties or other BURST supporting activities.

The two BMF pools are:

  • 1% pool-fee – BMF0-100
    • Recommended for miner which like to have „normal“ pool-fees
  • 50% pool-fee – BMF50
    • Reconmended for miner which like to spend 50% of the Blockreward to the BMF

 

 

 

Recent Tweets

For privacy reasons Twitter needs your permission to be loaded. For more details, please see our Datenschutzerklärung.
I Accept
For privacy reasons Twitter needs your permission to be loaded. For more details, please see our Datenschutzerklärung.
I Accept