Leicester

That process, once it's done, then they're saying there's an acknowledgement that it's been recognized on chain.

We see that it's recognized on chain.

We're good to go with it.

Now we're okay sending you the whatever currency or whatever product.

They have their own acknowledgement.

Let's say it's a crypto that they're sending you.

They have an acknowledgement that they got to wait through when they send it.

It's usually pretty quick because it's outbound, but they have an acknowledgement and that shows up in your wallet and then you're done.

And then yours, if you were to look at that transaction hash, you'll see on the actual scan, you'll see that there's a number of confirmations that keeps happening.

So it just keeps happening over time.

And this all goes to the integrity of the process.

in certain of these to make all this happen, to actually create the so-called network, to enable everything I just described, you have nodes.

The nodes are the heart and soul of what make the thing run in simple form.

And there's always multiple of them.

Part of the problem I would argue with nodes is, and this lends to the Sybil attack,

Part of the problem and the flaw with nodes is the assumption that everybody has the best of intentions.

As with any network, if your underlying servers, your routers, your computers, if you have a malicious actor powering this thing, it affects the network and drops its security and creates vulnerabilities.

Now with something like blockchain,

It's not like it could infect your computer or any of that because it's not running locally on your device, generally speaking.

But what it could do is it could compromise the value of your assets.