Burnt coins are added in explorer!
We display burnt coins for all period and for each block. Now burnt coins are 0.02% of circulating supply.

https://bgl.bitaps.com

Burnt coins    1 596.84031323 BGL

Encryption AES-CBC with key length: 256 bit

Our fowarding service with flat rate fee https://developer.bitaps.com/forwarding, successfully works several years. We use payment agregation to make payout transaction. 

Example https://bitaps.com/10282766f66076cd357ea8e437c819bf3d66b632b7ab62a7488756fec4e324e4

You can see in this transaction  that we agregate 10 payment and make 1 payout transaction. It works well enough to maintain flate rate fee.

0.0002 BTC this fee include forwarding transaction miners fee, bitcoin transaction is not free


At this moment no any fee, we are currently collecting statistics on the use of this service. In the future, the cost of hosting a 1 GB file will be about $ 5 per year.

Bitcoin encrypted paywall tool, allows you to create payment lock on files or a text message where user need to pay the assigned amount of Bitcoins to access the content. File content, file names and all messages including descriptions are encrypted in the browser. The service does not have access to content on its servers, so your media data is completely protected with AES encryption. Service charge flat rate fee 0.0002 BTC for each sale. Forwarding the payment to the seller's address takes place within 1-3 confirmations of the bitcoin network. Files and media data under 200MB hosted for free within 1 year. Files greater than 200MB hosted for free for 72 hours.

The Paywall link has a built-in password. Encryption password is part of this link after # character. All web browsers use URL standard. According to this standard, the part of the URL after the # character is an optional fragment. This fragment is only used on the client side(navigation on page) and web browsers do not send this part of the link to the server. Paywall service never knows or gets a password for server-side content. Decryption occurs only on the client side in the browser.

Bitcoin is not outdated technology

Upon request of EmmaWu we support Bitgesell wallet hackathon.

 Just created draft BGL JS library https://github.com/bitaps-com/jsbgl

Signed transaction working example
https://github.com/bitaps-com/jsbgl/blob/beta/test/jsbgl.test.js#L2112

https://bgl.bitaps.com/78c5454deb539ca6712a548ecef6b84061d79318a3ff565ce9854f403c37cc59

Example changes from jsbtc  to  jsbgl

https://github.com/bitaps-com/jsbgl/blob/beta/src/classes/transaction.js#L608

We invite everyone to contribute to this library

Hope it will help for Bitgesell wallet hackathon participants

Many withdrawal requests completed today!
Many new miners joined our pool!

Our congratulations to the entire community and invite to join the BGL mining with https:/pool.bitaps.com.

Our pool want to share a good news!

In gratitude for choosing our mining pool, we want to give a bonus to all our users!
Those participants who are now mining or already have mined coins will receive 200 BGL.
Participants registered only in our pool will receive 50 BGL.

Let's enjoy to take a part in new BGL coin minning, thank you for choosing our pool!

With best regards,
Team https://pool.bitaps.com

Take a look at https://www.npmjs.com/package/jsbtc.js

almost no dependencies
Crypto secp256k1 + wasm.
Implemented: bip32, bip39, bip44, bip49, bip84, bip141.
NIST random generation tests on the fly for entropy. Shamir's secret sharing for mnemonic.

In addition to the pool just started Block explorer for this coin, https://bgl.bitaps.com. Please add to official list. Thank you

Algorithm: Keccack

I use https://github.com/alexis78/ccminer for our GPU rigs


If you use our pool

Stratum URL: pool.bitaps.com:8888
 User: your_account@email.com.worker1
 Password: any

Just started mining pool for BGL coin.

https://pool.bitaps.com

• rewards type: PPS (PPLNS will be added same later)
• payouts:  daily by request (auto payouts will be added soon)
• pool mining fee: 1.5%

Pool settings:

 Stratum URL: pool.bitaps.com:8888
 User: your_account@email.com.worker1
 Password: any

Difficulty: variable by default, + manual settings available

Support email: support@bitaps.com

Is any open source miners available?

I'm developing now https://github.com/bitaps-com/btcapiserver

This is core for explorers or wallet backends. Python + Postgres.
Performance about 12 - 24 hours to initial parse bitcoin blockchain (depends of configurated modules and hardware)

Take look maybe my code will be useful for you.

The idea of separating filters by address type gives a significant reduction in the amount of required data requested by the light node. Refusing to divide by type will actually give a better degree of filter compression and the overall size will be even smaller than what we can achieve now. Block batch filters total size  is smaller then BIP 158 at all total size savings  22% (3.36 GB vs 4.3 GB). We could win another 3-4 percent. But assuming that mostly light nodes use only one type of address, separation provides significant gains in bandwidth reduction. Is the calculation of several additional hashes more important than reducing traffic several times?

In case we try use BIP 158 for commitment this is also  requires recomputing the commitment any time the txn list in the block is changed. Is additional double sha256 is so big problem? 
Also I think we can redesign commitment structure to exclude from commitment filter types which have no any affected script types in recent block it will solve problem with  out of date script types.

The idea is receive transactions flow with stripped data (inputs and outputs converted to distinct set of 4 byte items for specified filter type). And yes transaction flow means a lot of  sending the transaction. I got your point about "short id" will think how to implement it more properly.


I suppose that most common case light client receive about 2-3 payments daily, so in case we got positive test we be able use TOR with new identity and different nodes to request complete transaction. I think it should protect privacy Or am I missing something?

. Yes.

getcfproof is not use txid it use block hash. getcfproof is only actual in case we have commitments. In case no block filter commitments we should omit this step.

Have you read this one  https://github.com/bitaps-com/bips/blob/master/bip-block-batch-filters.mediawiki? any feedback about this draft?

Drafts updated

In context of compact signature format r and s  32 bytes, this is not about actual value

I don't understand why but people do it,  people do crazy things use a lot of IP, scripts, change addresses to prevent blocking to get more and more testnet coins

This is one of many examples:

https://tbtc.bitaps.com/2NBMEXavJZV2VoBCiRFHEJ8DehgYnfM9wav

8.34076971 tBTC   1 736 transactions.

We created a testnet faucet to help developers and did not expect to encounter inexplicable greed of people.