| 10:09 |
feedbot |
http://trilema.com/2020/rosalbas-awakening/ << Trilema -- Rosalba's awakening |
| |
~ 4 hours 21 minutes ~ |
| 14:31 |
whaack |
I would like some input as to what functions are necessary for a block explorer. There's really no end to all the features and different types of queries one can write and provide as an interface. So far I have prototypes for: utxos <address> , balance <address> , view-block <block-height> view-txn-by-hash <txn-hash> view-txn-by-pos <block height> <txn index> view-ancestors <block height> <txn |
| 14:31 |
whaack |
index> view-descendents <block height> <txn index> |
| 14:31 |
diana_coman |
whaack - the best way with sort of problem is to start with absolute minimum, have people use it and then ask+listen |
| 14:32 |
diana_coman |
nobody can tell you in advance "what's the best thing to design" but it will become clear as people use it, as simple as that. |
| 14:32 |
diana_coman |
with this* sort of problem |
| 14:33 |
whaack |
alright, i'll put one more function for viewing the rax hex of a block, start cleaning up the code, vpatch it, and then begin work on making a small web interface into the program |
| 14:34 |
diana_coman |
sounds like a plan; for sure best to get out a working minimal prototype and iterate *with practical use* than to spend whatever amount of time trying to get it perfect blindly like that. |
| 14:35 |
whaack |
sure. my guess is that the next big TODO item will be viewing txns in the memory pool since from my personal experience buying/selling bitcoins you want to see a valid txn has at least been broadcasted during the moment of a sale |
| 14:36 |
diana_coman |
so good, you just announced it, people can say something if they care and otherwise you have therefore already "what next" , all good. |
| 14:36 |
feedbot |
http://trilema.com/2020/the-making-of-a-cuckold/ << Trilema -- The making of a cuckold |