Thanks for asking. I use this as an invitation to explain, and give an update on my work ...
ABEESOIL 0.2.3 ...
I miss one of the most interesting functions: the transactions regarding an address
We all do.
It is not part of the
Ethereum API, as strange as that sounds.
I could not believe it myself, when I first encountered
the missing function.
A massively financed coin coding project doesn't even provide a list
of transactions to and from an address? They must be funny people.
I asked around a lot already. On gitter it was mentioned in September
"could do that as a weekend job" - but even now, it is still not there yet.
Github issues is full of requests about that topic.
How does it etherchain.org? There I can see the transactions
Yes.
I guess ...
etherchain has probably additionally built a private backend,
which has traversed all 800,000 blocks ...
... to extract more data than the data-parsimonious
ETH core developers are willing to give to us. A
surprisingly primitive base system:After having spent so much time creating
many cool apps on top of
the excellent and much older NXT API, where
all those beautiful API functions do exist, and with a really small blockchain ...
... it actually came as quite a surprise to me, that a hyped
(platform which is also used as a) currency is not allowing
users to look up transactions. ETH sucks, in that respect.
By the way, this same question is asked all over the net, in
several forums. But they say "impossible", or "too expensive", or
that they have more important things to do than solving this old issue.
Blockchain scanner backendI have come up with a workaround concept. Scan the whole chain myself.
One of the developers (
*) of that multi-million dollar platform ...
... is telling me (me who has been paid ~2-3 US-dollars / hour) that
I should do that work, and create a whole blockchain scanner backend myself.
Which I will probably have to do in the end. Yes. But I first want to make sure that I really understand what the tech is.
That scanner backend would be running as a 2nd process, observing
the chain, and accumulating more and more knowledge about it.
Research on getTransactions(account)I have done a lot of research in the past month ...
come on, and follow me into the abyss of
an overpaid, and underachieving platform *lol*
-->
- eth_listTransactions
= a looooong thread of many, many people wishing for the same function as you.
Within in:
- me asking how it can be solved with a FILTER (due to a misleading wiki manual)
- which TWO WEEKS later was finally answered ... with a NO, it can't.
- then me suggesting that if their system is too blind even about
such a basic object like transactions ... to please create a
blockchain-iterator-dump-results-into-database project,
for all of us who need such information. - And me being more precise about it, giving more examples.
- In the meantime (because there was no answer for so long),
I had opened a new full issue thread to ask for
"transactions of an address - example code please"
- which resulted in an interesting contract suggestion,
but of course, buying contracts, and storing information for all addresses on the chain
would actually cost money, so I guess that is not really a way to go to,
if you want such infos for ALL addresses.
- Moreover, it is being discussed to remove the concept of user accounts altogether!
The above is only a very VERY quick summary. More infos behind the links. Ctrl-Click them all.
I urge you to read both full threads, to understand the situation better.
It is actually quite interesting, and it helps a lot to understand more
about the backgrounds of ethereum, and its clones.
The supply is unknown!There is another real issue, and that is the
supply.
As far as I see it, no one really knows the REAL supply of ether. Or soil.
Really. Similarly absurd like the above unsolved question.
The background are
uncles, and their rewards.
Until now, I still have not even got
one answer from any of those ETH devs,
if
my assumed formula is correct or not.
Asked again, nothing.
By now I suspect most people don't care, or just don't have a clue.
I was told that I am
the first one who has ever asked. Strange.
The supply of ether is often wrongly given only as
blocknumber * blockreward + premine.Which is
not correct.
The whole supply is larger, as there are uncle rewards
(the new bitledger.net is showing them nicely).
But the ETH node itself does not know how many uncles have been mined
*lol* They have created a funny system, or rather: It is simply unready.
Read this whole issue thread, interesting:
getUncleCount(fromBlock,toBlock) - or: Doesn't total supply depend on uncle count?All this research above, and much more which is not published
(presentation & communication is a huge time eater) ...
... is necessary preparations for the next step.
The past and the futureAll in all over 40 hours of work went into this now, the above research alone
took ~10 hours. Until today (additional to the ~7 hours negotiations before,
plus
dozens of hours that I have
already put into soil), the
summary for ABEESOIL work is:
14.2 hours coding
5.3 hours system
2.5 hours orga
5.4 hours communication
6.1 hours presentation
10.5 hours research
I have succeeded in porting my ABEE 0.2.2 to SOIL,
and adding a few improvements on the way -->
0.2.3aNow the next steps can be planned.The
*
getAllTransactionsOfAccount and the
*
realTrueHonestSupply are not the only future functions on the wishlist.
It would also be nice to be able to find out more about compiled
* contract "code" on e.g.
this page.
Once the whole blockchain gets scanned, I would like to see the
* difficulty evolution, and
* blocktimes over time.
More functions that you would like to see, please describe them here. Thanks.And thanks to everyone who has been, and will be supporting me and my work.
Don't you think this text here, and all those linked posts are ... interesting?
Right? Then you can do your part now, to ensure that such splendid intellectual
pleasure can and will continue in the future, and everything improves, and grows
;-)
TL;DR: -->
If you like it, show it
[SOIL] 0x8da4fc05ca343e6a41646194e91931d9f413a40c
BTC 1M4EaZVprZEmtrS3G78fMFy8yGVgdUJMXv
Thanks.