Quote from: ETFbitcoin on October 20, 2021, 09:12:32 AM

Quote from: megasyl on October 14, 2021, 08:24:44 PM

Maybe I'll make something to talk directly to your node with RPC so I can use extended public keys to derivate addresses without the risk of exposing it (and read data directly, without limitations). (I'm thinking about the umbrel app store for exemple)
I also use their websocket api to live update the transactions.

Bitcoin Core doesn't have index of address, so it'll be challenging task unless the input is changed to both address and any TXID which contain that address (assuming the local node enable txindex).

Quote from: megasyl on October 14, 2021, 08:24:44 PM

What do you think about it ?

I like it, the UI is simple and doesn't feel bloated. Do you have any plan to make your tool open source?

I'm not sure yet how to do the index part. If I can use an external one like electrum's index (because I have a node running electrum) but I don't know if it can help. Maybe I can use an external tool to index it myself but that would require extra space :/
I'll probably make it open source yeah Cheesy

Quote from: SFR10 on October 20, 2021, 10:30:43 AM

Quote from: megasyl on October 18, 2021, 04:58:22 PM

The address API route is still called via the browser so every user will have it's own limit rates.

I have no idea how exactly those limits are imposed, but it seems that it's not just tied to each individual ^{[each of the browser's sessions, led to a different result (tested in Chrome, Tor, Firefox, Opera, and Edge)]}.

Quote from: megasyl on October 14, 2021, 08:24:44 PM

when you open big addresses it crashes,

It's worth noting that I experienced more crashes while it was "zoomed in".
^{- Perhaps it's hitting some of the limits in your current hosting plan ^{[apart from the API limits]}.}

I noticed that the "X" button, doesn't work.

Despite all of the above issues, I really enjoyed using it ^{[when it's working smoothly]}

^{- Bookmarked.}

.

The interface is generated by a browser code, the rendering has nothing to do with the hosting plan (unless you take into account the time to serve the script to the browser).
I'm using a library (react flow) which ... was maybe not really made to be stressed with big transactions.
I'll probably optimize the interface by, for exemple, not rendering the input/output addresses of a transaction if it has more than x input/output, and add an option to expand it at will.

And sorry for the missing feature, I do it after work when I'm bored ahah.

I'm glad you liked it Cheesy

Quote from: FatFork on October 20, 2021, 09:12:44 PM

The preview looks like a really interesting concept, and it could be a useful tool. However, I was unable to open the application.
My CPU was at 100% and nothing happens for more than ten minutes, so I sometimes had to kill the process to terminate the application.

Sorry you didn't have a good experience :/ Try with small transactions first and see what are your limits. I'll try to improve the performances :p