The Bi-Weekly Burst Report is produced under the flag of the Burst-Alliance, a community-driven initiative comprised of developers and highly motivated Burst ambassadors. We welcome anyone to join us and show their support
Visit us on Discord in #marketing-and-bmf and #burst-apps-team
Check the activities with the following links for the main repos:
Note: This only includes a portion of the activity from the Burst Apps Team
- Account Activation Service launched
Newly created Burst accounts are considered insecure until the owner executes a transaction. Doing so, a public key is being assigned to the account and though securing the account. To execute a transaction the owner needs at least some minimum balance to pay the fee for his first transaction. This was handled through the faucet system, where users could get some burst automatically. Unfortunately, this faucet used to be abused by certain individuals.
BAT member ohager created a way to assign a (matching) public key to an account without the need of an outgoing transaction. This is considered as account activation. The account activation can be done manually using the web application, or using the web service to activate accounts programmatically.
- Phoenix supporting Account Activation
The new account activation was also integrated in Phoenix and will be released very soon with Version 1.0.0-beta.12
- Deeplink specification (CIP22) implemented in BRS
The recently presented specification for deep links (CIP22) was implemented in BRS Version 3 by BAT member ohager. The API was extended by two new endpoints (namely: generateDeeplink and generateDeeplinkQRCode) that allows consistent deep link generation as URL or QR Code. With deep links it’s possible to make applications interoperate better, e.g. sending messages from within one application using another.
- New Version of Mobile Wallet for Android released
- New Version of BurstJS (0.4.3) released
The new version improved developer experience using interfaces instead of long argument lists. The API settings are simplified also, and the Http module (based on axios) supports additional configuration, making the it more versatile
- New spoiler from the upcoming Burst-DEX
- Yelling corp supported MMA fight
BMF Weekly Funds Report
The BMF owns 5 accounts with the following balances:
- BMF#1: Marketing
1,067,312 BURST (-1,173)
- BMF#2: Exchange Listing
537 BURST (+0)
- BMF#3: Development/Bounty
501,504 BURST (-120,000)
- BMF#4: Hackathon
0 BURST (-0)
- BMF#5: Faucet Account
4067 BURST (+102)
- BMF 0-100 Pool to help sustain marketing and development
BMF has announced a new 0-100 pool with a 1% fee, which will be dedicated to BMF-related activities like hackathons, bounties, advertisements, etc. We encourage miners to mine some extra space against this pool, as this is going to a good cause and helps keep things running like this very Burst Bi-weekly Report.
- NDS-A now paid by script – every 10 hours
The BMF (BURST Marketing Fund) is paying now the NDS-Award (Networtk-Distribution-Strengthen) every 10 hours to the node operators with valid BURST- addresses, newest BRS version (current BRS 2.4.2) and was seen with the payment of the reward. The NDS-A will be paid from the BMF NDS-A Distributor account.The crawler from https://explorer.burstcoin.network/ is used to identify the valid nodes for the NDS-A.The interval is setup as a subscription from the BMF account with 110 BURST every 10 hours. The payment is fully automated in that way that everyone can send BURST to BMF NDS-A Distributor to distribute the BURST to the node operators. This script was provided by BAT developer Zoh! To participate in the NDS-A, you only need to operate a full-node with the current BRS version 2.4.2 and set your P2P.myPlatform to your BURST account. In your BRS config file set “P2P.shareMyAddress = yes”.Your node is connectable tcp/8123 “P2P.Port = 8123” Download the Qbundle 2.5.3 here and read the manual for the installation.
Tweets of the week
The Burst Apps Team has agreed to support new and existing exchanges wishing to list BURST. Exchanges may contact firstname.lastname@example.org for technical support.
The author does not endorse and does not take responsibility for any project mentioned in the Weekly Burst Report. All content is for informational purpose only and is not financial advice