Topic: Byteball - Round 9 - full moon of September 6, 2017 at 07:02 UTC

[vindyne8]

For full technical description, read the white paper: https://byteball.org/Byteball.pdf

Exchanges: https://cryptox.pl and trading bot (see the link at https://byteball.org)
Auctions: #auctionroom channel on our slack http://slack.byteball.org
Explorer: https://explorer.byteball.org

Download the wallet:

iOS   Android   Mac   Windows   Linux
or build from source at github

Desktop wallets can be full nodes (will take a while syncing with the network after the first start) or light nodes.  Mobile wallets are always light clients.

If you want to experience the wallet without paying a penny, visit https://byteball.org/testnet.html to install testnet wallet and click the link to receive free bytes to play with.  The link will open your wallet:

The design

There are no blocks in Byteball, and no block size issue.  Instead, every new transaction references one or more earlier ones (parents) by including and signing their hashes.  The links among transactions form a DAG (directed acyclic graph):



By including its parents, each new transaction also indirectly includes and confirms all parents of the parents, parents of the parents of the parents, and so on.  As more transactions are added after your transaction, the number of confirmations you receive grows like snowball, that’s why the name Byteball (our snowflakes are bytes of data).

Consensus

There is no PoW, no PoS, and no mining.  Instead, we have the DAG, which already establishes partial order between transactions, plus we add the main chain within the DAG:



The main chain (MC) allows to define total order between transactions: the transaction which gets included (directly or indirectly) earlier on the MC, is deemed earlier in the total order.  When there is a double-spend, the version of the transaction that comes earlier in the total order is deemed valid, all others are deemed void.

The main chain is defined deterministically based on the positions of transactions in the graph.  Refer to the white paper for details, but as a general rule, the MC gravitates towards transactions authored by well known users, which we call witnesses.  The list of witnesses is defined by users themselves as they include the list in every transaction they post.  The MC then follows the path within the DAG such that:
1. the witness lists of the neighboring transactions on the chain are either identical or differ by only one mutation,
2. the chain goes through the most number of witness-authored transactions, compared with alternative chains.

The above is very brief and sketchy description with many important details omitted, refer to the white paper for a full technical story.

Fees and intrinsic value

The fees paid for storing one’s transactions (or any other data) in the Byteball database are equal to the size of the data being stored.  If the size of your transaction data is 500 bytes, you pay exactly 500 bytes (the native currency of Byteball) in fees.  This means there is intrinsic value in bytes: it is the utility of permanently storing that size of data in a decentralized immutable database.  For data that represents financial transactions, the value is social rather than personal, because you absolutely need to store the full coin history in order to be able to prove the value and authenticity of the coin to each subsequent owner.

The fees are collected partially by those who are first to reference your transaction as parent and partially by witnesses.  The former incentivizes referencing the most recent transactions as parents, which results in the DAG growing in one direction only, like the trunk of a tree, and being as narrow as network latency permits.  If new transactions are rare enough, such that all nodes have enough time to sync before a new transaction appears, the DAG will look almost like a chain, with only occasional forks and quick merges.

Money supply

The total number of bytes is 10¹⁵, all bytes will be issued in the genesis transaction. Since the fees paid are returned into the circulation, the money supply will remain the same.

Deterministic finality

In Byteball, there is a protocol rule that a transaction must include the previous transaction (if any) sent from the same address, i.e. there must be partial order between subsequent transactions from the same address.  Breaking this rule is considered equivalent to double-spending, therefore at least one of such unordered transactions will become void.  If we assume that most witnesses follow this rule (that’s what they are elected for), they have to reference only sufficiently recent transactions as parents and can’t inherit from old enough parents.  Therefore, they can no longer influence the MC (which is attracted to witnesses) in the old enough part of the DAG, and that part of the MC becomes stable, hence the total order relative to this MC also becomes stable.  See the white paper for discussion of exact criteria of reaching stability, here it is important that the criteria are deterministic, and once a transaction appears on the stable part of the MC, it is final, and, unlike all other cryptocurrencies, no re-orgs are possible. 

This is extremely important for applications in financial industry and for wider adoption in general, as most people are used to expect certainty in matters of money and property ownership, and the concept of probabilistic finality is a difficult sell.

Assets and on-chain exchange

Bytes is the native currency of Byteball.  Users can issue any other tokens (assets), e.g. to represent debt.  The debt can be expressed e.g. in fiat currencies or in natural units (barrels, ounces, kWh, etc).  The issuers of the debt can reveal their real-world identities and/or be voluntarily attested (i.e. their real-word identities be verified by a well known third party such as CA).  This enables the use of the existing legal system to secure against fraud.

The issued assets can be used as means of payment, along with bytes.  Assets can be exchanged against bytes and other assets by both parties signing a single unit that executes both legs of the exchange, thus the two transactions either happen simultaneously or don't happen at all.  This kind of signing is called multilateral signing.  No centralized exchange is needed, hence no trust is necessary and no exchange fees (apart from the usual fees for the size of the data).

Private untraceable payments

Assets can be either public or private.  All transactions in public assets are visible to everyone on the public decentralized database, just like Bitcoin.  Bytes is a predefined public asset.

Payments in private assets are not published to the public database.  Instead, only the hash of the transaction is stored to the database, while the plaintext of the transaction is sent directly from the payer to the payee.  To protect against double-spends, a spend proof is also published to the Byteball database.  The spend proof is constructed as a hash of the output being spent, so that if the same output is spent twice, the spend proofs will be necessarily the same.

I’ve already described this design at https://bitcointalk.org/index.php?topic=1574508.0, see more details in the white paper.

Regulated assets

Regulated institutions can issue assets that are compatible with KYC/AML requirements. Every transfer of such asset is to be cosigned by the issuer, and if there is anything that contradicts the regulations, the issuer won't cosign.

This way, banks can issue fiat-pegged assets and stay fully compliant.  They can open demand deposit accounts and track them on Byteball as assets.  These assets are easily exchangeable against bytes and other assets (with bank’s approval).

Other features

- Spending conditions (AKA smart contracts) in an easy to understand declarative language https://bitcointalk.org/index.php?topic=1617816.0
- Multisig: a special case of spending conditions
- On-chain oracles can post data (such as timestamps, exchange rates, weather, various events) directly to the database, then that data can be referenced from spending conditions
- Private end-to-end encrypted messaging: used to convey private payment data, communicate in multisig scenarios, and chat with a merchant’s bot.

Initial distribution

There will be no ICO, no crowdsale.  I believe the success of a currency depends on the number of people who own it, in fact Peter R’s research suggests that historical marketcap of Bitcoin follows Metcalfe's law: https://bitcointalk.org/index.php?topic=572106.0, i.e. it is proportional to the square of the number of active users.  That’s why I want Byteball to be in the hands of as many people as possible:


98% of all bytes and blackbytes (the private untraceable currency) will be distributed among bitcoin holders who link their bitcoin and byteball addresses before any of the distribution rounds.  No investment required, you keep your bitcoins, plus receive the bytes and blackbytes.  See below how to receive the coins.
1% I reserve for myself


Current status

The network was launched on December 25, 2016, and 10% of bytes and blackbytes distributed to those who linked their Bitcoin and Byteball addresses.  The total balance linked was over 70,000 BTC.  In the second round, we distributed another 1.76%, over 120,000 BTC was linked.

Participation in Byteball distribution

If you missed the 1st and 2nd rounds of distribution, you can still participate in the further rounds.  If you already participated or bought bytes on an exchange, you can multiply your holdings. 

The snapshots for the 3rd round will be taken on the Full Moon of March, on March 12 at 14:54 UTC.  In this round, you receive:
- 62.5 MB for every 1 BTC of proven balance
- 0.1 new bytes for every 1 byte you own at the moment of the snapshot

You also receive blackbytes:
- 62.5 * 2.1111 * 10⁶ blackbytes for every 1 BTC of proven balance
- 0.21111 new blackbytes for every 1 byte you hold on the linked address at the moment of the snapshot
(total money supply of blackbytes is 2.1111 times more than that of bytes)

To participate, link your Byteball and Bitcoin addresses before the 3rd round:

1.  Download and install the wallet by following the above links.

2.  Visit https://byteball.org and click the link to chat with the Transition Bot.  The link will open the new wallet and start a chat.  Follow the instructions of the Transition Bot to prove your Bitcoin balance.

You have two options to prove your Bitcoin balance:
a.  By making a micropayment.  The bot will see your address the payment came from, will know that it is your address, and will instruct you to move your Bitcoins to this address.  By making several micropayments, you can link several Bitcoin addresses to the same Byteball address.
b.  By signing a message (if your Bitcoin wallet supports this function).  You tell the bot your Bitcoin address and sign your Byteball address with the Bitcoin address.  After you prove one address (a typical Bitcoin wallet has dozens of them), you can either move all your coins to this single proven address or prove all other addresses in the same way -- by signing a message. 

If you try to link the same Bitcoin address to multiple Byteball addresses, both links are ignored.  If you did this by mistake, link another Bitcoin address.

If you prove by micropayment, remember to check that the Bitcoin address that the bot received the micropayment from, is indeed your address.  An attacker might see your payment on the blockchain and repeat the same micropayment from his address trying to trick you to move your funds to him.

3.  If you make any Bitcoin payment, your coins will most likely be moved to a new change address.  Chat with the bot again, see the balance on your linked address(es) and move the coins back to the linked address(es) if necessary.

The linking phase will end on March 12 at 14:54 UTC, after which we'll do the distribution in proportion to BTC and bytes balances on this date.

In the 3rd round, we'll distribute as much as is linked and calculated by the above rules, the exact % is not known in advance. 

The 4th and subsequent rounds (yet to be announced) will follow similar rules, but the relative weight of bytes vs. BTC (i.e. which amount of bytes gives the same share in the new distribution as 1 BTC) in the 4th and further rounds will change and will gradually increase to 1 BTC=62.5 MB.  It will be selected to maximize the value of bytes and keep the speed of distribution in sync with the growth of user base and the actual use of the network.  The ratio 62.5 MB per 1 BTC is chosen so that the total money supply of bytes (10¹⁵) and the total number of BTC in circulation (16,000,000) are equivalent.

We'll have as many rounds as is necessary until all bytes are distributed, most likely a new round every full moon.

My 1% doesn't participate in the 2nd and further rounds.

Earlier adopters have the opportunity to participate in greater number of distribution rounds and receive new bytes in each round by using the same BTC balance and bytes received in the previous rounds.  You are effectively multiplying your stake in each additional round you take part in.

Track the progress of linking at http://transition.byteball.org.

How you can help

- play with the wallets, install them on multiple devices, pair them for multisig.  If you find bugs, report them.
- run a relay on your cloud server to help the network. The relay doesn’t hold any private keys, so you don’t have to worry too much about security.  Get relay source code from https://github.com/byteball/byteball-relay
- run a hub to better decentralize the delivery of private payments (the hub also includes a relay).  Again, the security doesn’t matter much as all messages are end-to-end encrypted.  Hub address can be changed by users in their wallet settings.  Get hub source code from https://github.com/byteball/byteball-hub
- fix bugs, contribute improvements in our github repositories https://github.com/byteball.  In particular, we need faster syncing and faster UI.  Before now, I prioritized simplicity of algorithms over performance, now we need speed too.  A 10x improvement should come easy enough, the next 10x will be probably harder.  Discuss any major changes before actually implementing them.
- develop new tools/apps that you think will be useful for Byteball users
- spread the word about Byteball and remember that its value is proportional to the square of the number of active users


Translations: Chinese, French, German, Hindi, Indonesian, Italian, Japanese, Korean, Portuguese, Russian, Spanish, Turkish.

Twitter: https://twitter.com/ByteballOrg
Slack: http://slack.byteball.org
Telegram: https://telegram.me/byteball
QQ: 326176030
WeChat: Byteball 中国 https://twitter.com/ByteballOrg/status/830071965188812800

-----------------------------

One last thing.  The remaining 1% will be given away to the first 100m users who install Byteball wallet, 100 Kbytes to each user.  This will start 6 months from now or later, after we get ready for that scale.

[vindyne8]

[vindyne8]

#Byteball version 0.6.0 released.  Important bugfixes https://github.com/byteball/byteball/releases

[vindyne8]

Quote from dev of Byteball:

Finally, you can experience the pre-distribution linking of Byteball and Bitcoin addresses.

We are launching a new testnet, and you'll be able to get a portion of its distribution in proportion to your balance in Bitcoin testnet.

0.  Get your Bitcoin testnet wallet ready and funded.

1.  Download and install the wallet for the new Byteball testnet: https://github.com/byteball/byteball/releases
You will have two Byteball wallets - one for the old testnet that you already have, the other for the upcoming new testnet.

2.  Visit https://byteball.org and click the link to chat with the Transition Bot.  The link will open the new wallet and start a chat.  Follow the instructions of the Transition Bot to prove your Bitcoin balance.


You have two options to prove your Bitcoin balance:
a.  By making a micropayment.  The bot will see your address the payment came from, will know that it is your address, and will instruct you to move your Bitcoins to this address.  By making several micropayments, you can link several Bitcoin addresses to the same Byteball address.
b.  By signing a message (if your Bitcoin wallet supports this function).  You tell the bot your Bitcoin address and sign your Byteball address with the Bitcoin address.  After you prove one address (a typical Bitcoin wallet has dozens of them), you can either move all your coins to this single proven address or prove all other addresses in the same way -- by signing a message.

If you try to link the same Bitcoin address to multiple Byteball addresses, only the last linking counts.

If you prove by micropayment, remember to check that the Bitcoin address that the bot received the micropayment from, is indeed your address.  An attacker might see your payment on the blockchain and repeat the same micropayment from his address trying to trick you to move your funds to him.

3.  After linking, there is no use of the new wallet before the distribution, just keep it installed (backup if necessary).  It will receive the bytes on the distribution day.  If you make any Bitcoin payment, your coins will most likely be moved to a new change address.  Chat with the bot again, see the balance on your linked address(es) and move the coins back to the linked address(es) if necessary.

The linking phase will end in late November, after which we'll do the distribution for the new testnet.  Those who linked their Byteball and Bitcoin addresses will receive new test bytes in proportion to their Bitcoin testnet balances on the distribution day.

If all goes well, we'll do exactly same linking, but with real Bitcoin addresses, from early December to December 25 before the upcoming livenet launch and distribution.

[vindyne8]

A few Q & A from the past week:





Join #Byteball on slack to keep up on current events!

[vindyne8]

Byteball version 0.7.0t released: huge performance improvements and new testnet.
Get it here: https://github.com/byteball/byteball/releases

[vindyne8]

From the Byteball dev:

Starting now, you can link your Byteball and Bitcoin addresses for the upcoming distribution.

1. Download and install the wallet for Byteball live network:
Desktop: https://github.com/byteball/byteball/releases
Android: https://play.google.com/store/apps/details?id=org.byteball.wallet
* You will have two Byteball wallets - one for the testnet that you already have, the other for the upcoming live network.

2. Visit https://byteball.org and click the link to chat with the Transition Bot.  The link will open the new wallet and start a chat. Follow the instructions of the Transition Bot to prove your Bitcoin balance.

You have two options to prove your Bitcoin balance:
a. By making a micropayment. The bot will see your address the payment came from, will know that it is your address, and will instruct you to move your Bitcoins to this address. By making several micropayments, you can link several Bitcoin addresses to the same Byteball address.
b. By signing a message (if your Bitcoin wallet supports this function). You tell the bot your Bitcoin address and sign your Byteball address with the Bitcoin address. After you prove one address (a typical Bitcoin wallet has dozens of them), you can either move all your coins to this single proven address or prove all other addresses in the same way -- by signing a message.

If you try to link the same Bitcoin address to multiple Byteball addresses, only the last linking counts.  This rule might be adjusted if we see attempts to link exchange-owned addresses.

If you prove by micropayment, remember to check that the Bitcoin address that the bot received the micropayment from, is indeed your address. An attacker might see your payment on the blockchain and repeat the same micropayment from his address trying to trick you to move your funds to him.

3. After linking, there is no use of the new wallet before the distribution, just keep it installed (backup if necessary).  It will receive the bytes on the distribution day.  If you make any Bitcoin payment, your coins will most likely be moved to a new change address.  Chat with the bot again, see the balance on your linked address(es) and move the coins back to the linked address(es) if necessary.

The linking phase will end on December 24 at 23:59:59 UTC, after which we'll do the distribution in proportion to Bitcoin balances in the first block timestamped after December 25 00:00:00 UTC (Christmas block).  I'll announce the exact block number several hours after this block is mined (the waiting time is to exclude the slightest chance of reorg). The bytes and blackbytes will be sent out in the afternoon of December 25.

During this distribution we'll distribute 10% of the total supply of bytes and blackbytes. The remaining 88% will be distributed during subsequent distribution rounds, exact dates to be announced later. The planned distribution percentages (subject to change):

2nd round: 20%
3rd round: 30%
4th round: 38%

The rounds will be spaced 1 to 2 months.

In each subsequent distribution round, we'll take a new snapshot. The distribution rules in the 2nd and further rounds will be slightly different from the 1st. You'll show both your BTC balances (as in the 1st round) and your balance in bytes (which you received in earlier rounds or bought from other users). You have a sort of basket that consists of a mixture of BTC and bytes. To determine the weight of the basket, every 62.5 MB are counted as 1 BTC. For example, if you have 125 MB and 3 BTC, the weight is 2+3=5 BTC. The distribution of new bytes in the 2nd and subsequent phases will be proportional to the weight of your basket.

My 1% doesn't participate in the 2nd and further rounds.

The ratio 62.5 MB per 1 BTC is chosen so that the total money supply of bytes (10¹⁵) and the total number of BTC in circulation (16,000,000) are equivalent.

Earlier adopters have the opportunity to participate in greater number of distribution rounds and receive new bytes in each round by using the same BTC balance and bytes received in previous rounds. You are effectively doubling your stake in each additional round you take part in.

Please retweet https://twitter.com/ByteballOrg/status/806290785486467073

[vindyne8]

Some distributions stats: http://transition.byteball.org/

Total balance linked: 11046.67590134 BTC

Current transition rate: 0.11046676 BTC/gigabyte

[vindyne8]

Questions from the community, and answers from the dev, from the main BCT thread.

Question:

Hi tonych,
After this 25th snapshot, byteball and blackbytes will be distributed as per the rules you announced.
Byteball will be send to linked byteball addresses that reside on "byteball public DAG", I can understand this is completely asynchronous process..
What I cannot understand is about blackbytes distribution:
1) Is it an automatic or interactive process (need human intervention)?
2) Will byteball client with the linked keys on peoples computers need to be left running to receive these coins?
Thanks again.

Answer:

1) It is automatic.
2) Not necessary, you'll see both bytes and blackbytes as soon as you start the wallet after the coins are sent out.
- tonych

Question:

Tonych, is the model sort of proof of service? Those that relay the activity and transactions get rewarded some bytes? I read the whitepaper but still am looking for some sort of understanding of this.

Answer:

It is not a proof-of.
The collected fees are split between regular users who are first to extend the DAG and witnesses who help define the order of transactions.
-tonych

Question:

Why it is not instant? say if there are 1000 tx per second in the network, my transaction once done will be covered within a second by 50 other transactions, isn't that after 1 second my transaction will have 50 confirmations? If we put 10 confirmations as confirmed, isn't my tx is confirmed after less than 1 sec?

Answer:

Perhaps you got used to hear about N confirmations in Bitcoin.  There is no such thing here, your transaction is either final or not.  And getting covered advances it to being final.  Getting covered by witnesses matters most (the structure of the DAG after your transaction also matters for finality).  Witnesses earn fees from transactions they cover, and the more transactions per second there are in the network, the more frequently witnesses will post with positive ROI (they pay fees like everybody else).

You will never get sub-second confirmation times because of network latency.
-tonych

Question:

OK so if I got it correctly, then if the transaction are covered by more than half witnesses' transactions it will be final thus confirmed? Are witnesses always emit transactions? What if none of the witness are doing tx? my tx will never get confirmed?

Answer:

It'll do as a very rough approximation, see the white paper for the exact criteria of finality.
Witnesses are expected to always emit transactions, that's one of the factors that determines the choice of witnesses.
-tonych

Question:

This is interesting question. Suppose, each of 12 witnesses run a script which submit transactions at crazy rate, but nobody else is using the network at this time. What happens then? Do witnesses end up loosing money?

Answer:

Witnesses do post transactions automatically but do it in a bit more reasonable way https://github.com/byteball/byteball-witness/blob/master/start.js
-tonych

Question:

is there any way planned to increase marketing apart from the sig campaign ?

I think this project will only succeed if we have a lot of users.

Answer:

Any suggestions are welcome.
We have sig campaign, twitter campaign, and a recent press release which resulted in a few publications.
-tonych

Question:

Quick Question; can we link multiple BTC addresses to our one Byteball address by sending the micro transaction from each BTC address, and do we have to run the Transition Bot each time?

Answer:

You can (if you can control which address the payment is sent from, this is an advanced feature).  You just send the same micro-amount to the same address.
-tonych

Reply:

Incidentally, I finished developing our trustless exchange bot a day ago, just when you started this discussion.  How did you know?
It will exchange only internal assets, not a replacement for poloniex etc.
-tonych

Question:

Please provide some more details? how to use it? what internal assets you meant? Is it blackbyte? I don't see any other internal assets...

Answer:

I'll release it in a few days, need to make a few changes to the wallet too.
This version of the exchange will work with public assets only, blackbytes are private.
tonych

[vindyne8]

Less than 2 days  remain to link your BTC address for Byteball distribution!
Don't miss out, visit https://byteball.org/ and https://bitcointalk.org/index.php?topic=1608859.0 for more information!

Recent updates from the dev: tonych are quoted below

Two news for today: version 0.8.0t is released and trustless exchange is launched.

Both are for testnet.
Download the new version from https://github.com/byteball/byteball/releases, Android should auto-update, and the link to the exchange is at https://byteball.org.  Only the new version will work with the exchange.

The exchange allows to exchange public assets issued on Byteball platform, including bytes.  Blackbytes are not covered as they are a private asset.

The exchange is not built-in (as in Nxt, Ripple, and Bitshares), it is an application built on smart contracts.  It is the first application on our network that uses smart contracts.  By keeping the exchange out of the core, we achieve that we don't have to add complexity to the core, as well as greater flexibility in how the exchange can work.

The exchange is centralized and trustless.  Centralized means that there can be many centralized exchanges competing with each other and trying to deliver better product.  Centralized also means that it is run as a business and can be properly managed and marketed.  Trustlessness means that the exchange operator can't steal customer's money, nor can he lose it if the exchange is hacked or mismanaged.  This is achieved by very simple smart contracts that every user can see and verify, and he doesn't need to be a developer to understand them:

To create an order to exchange asset A to asset B, a customer sends his asset A to an address that can be spent:
- by the customer himself after a timeout, or
- by the exchange operator if the same transaction simultaneously sends asset B to the customer (in the specified amount)

The first clause allows the customer to cancel the order and take his money back.  The 2nd clause doesn't give the operator arbitrary control over asset A: the operator can use asset A only if he simultaneously pays asset B to the customer.  This is the key difference from conventional trustful exchanges -- the operator is bound by the contract.

The operator then matches this order with a reverse order from another customer and signs for both sides of the deal simultaneously.

This is what a typical dialog with exchange operator looks like (yes, it is a chatbot, you've already got used to):



Before paying, the customer is presented with a user readable description of the contract:

HXY5... is the asset we are buying (chips).
W272... is the exchange address (actually, it doesn't matter who owns this address as long as the asset is sent to us).

Before the order is executed, the customer can see everything about this smart contract address in his wallet -- its balance and history, and can spend from this address (after the timeout specified in the contract).  The address is presented as a subwallet, it is easy to navigate to and from.

For those who have experience with conventional exchanges, there are a few differences that may seem odd.  Due to how the smart contracts work, there is no partial matching of orders.  To overcome this, orders are split into a small number of standard sized orders.  The standard lot sizes are powers of 2, which allows to match equal-sized orders, as well as some common combinations thereof, such as one large order against two half-sized orders (e.g. 32=16+16).  (Instead of powers of 2, we could also use Fibonacci numbers as standard lot sizes because each size would be equal to the sum of two smaller sizes, e.g. 13=8+5).  That's why when you create an order you usually pay to several addresses.  These sub-orders can match at different time and you'll receive your assets in several standard-sized portions.  Also, placing an order is not instant, you have to wait that the transaction that funds it becomes final.  Obviously, there is no margin trading, and there are no charts in chat.  So, if you are a day trader, it is not for you.  If you need to occasionally buy or sell assets, I think this tool is quite good for you.

Try it for yourself, the new UI is available after upgrading to 0.8.0t, and the link to start a chat with the exchange bot is at https://byteball.org.  Remember, this will work with testnet wallet only.

Please retweet https://twitter.com/ByteballOrg/status/811007135148572672

Transaction explorer is online https://explorer.byteball.org

It is the coolest transaction explorer in crypto, isn't it?