Quote from: stwenhao on Today at 10:17:24 AM

Quote

i just wonder why this part of original implementation never became bigger?

Because of Occam's razor.

Quote

it has no mining power scaling showing for the user using it and it is just used for making transactions itself basically

Exactly as intended, here is another Satoshi's quote:

Quote from: satoshi on May 18, 2010, 08:06:46 PM

Simplified Payment Verification is for lightweight client-only users who only do transactions and don't generate and don't participate in the node network. They wouldn't need to download blocks, just the hash chain, which is currently about 2MB and very quick to verify (less than a second to verify the whole chain). If the network becomes very large, like over 100,000 nodes, this is what we'll use to allow common users to do transactions without being full blown nodes. At that stage, most users should start running client-only software and only the specialist server farms keep running full network nodes, kind of like how the usenet network has consolidated.

Also, for that reason, you don't have built-in miner in the Core client, you have only some bitcoin-cli commands like "generateblock", but they are needed mostly on regtest, and not intended for mainnet use.

Quote

i wonder where the problem is for that?

You should make a separate application, that will talk with the Core client, that will be easier. If you try to integrate everything into the official client, you will see, why it is a bad idea. But if you want to try, then download the most recent version from GitHub, and explore it by yourself, if you are not convinced. In the worst case, you will end up with your own altcoin, in the best case, it will evolve into an alternative, minority client, that will be fully compatible with the official one. By walking this path, I hope you will end up with some separate application, but well, it will be your choice.

Quote

so why not giving a bit more space for more data for newers times build functionalities?

Ordinals blocked any block size increases above 4 MB. They set that limit in stone, if anything, it could be lowered, but not raised. As a recent example of that is OP_RETURN pull request, that was blocked as controversial: https://github.com/bitcoin/bitcoin/pull/28130

i understand your concerns. but you also showed me quotes from a later time.
this is 0.0.8

at this moment it is the year 2008 inside this threads running simulation for understanding this better. not todays time! at least for direct code discussions.

so what i can say it has a bitcoin generator implemented that originally was the mainnet build for having it coming to life to pay for the work having to be done. but a mainnet history besides code files did not exist yet at that time.

i really just wanna work with inside this limitation and only where i have switch into 0.1.0 so try to give me a bit of a chance here. newer code above 0.1.0 is irrelevant mostly for this thread.

as said as a simulated thing. for this we have to exclude newer things for now. unless i see them relevant to take into consideration.

i make an exception for 0.1.0 or for things that did build later that can be insipiring for understanding this old time better.

but it is not helpful working with problems from later builds here or limitations being set for blocksizes and such.

we have 1 megabyte here not more! so we have to find ways to get more out of this now. not by increasing but by optimizing how its being dealt with!