BitcoinJS VS turf

Reference | Code on Github

Inspired by the popular Coinb.in open source wallet and powered by bitcoinjs-lib, my hot wallet is designed to provide a secure and easy-to-use experience while also adding unique features that make it stand out from the competition. It will be installable (PWA) and very easy to use (BEGINNER FRIENDLY). I'm also going to make it open source. Other cool features like an HD wallet option with auto-change address after every transaction, increasing security and anonymity, are on the roadmap.

You could also probably rely on a JS library to do the above: https://github.com/bitcoinjs/bitcoinjs-lib

Checkout the bitcoin sdk for a language of your preference and try, this can help build the transaction. Javascript for example: https://github.com/bitcoinjs/bitcoinjs-lib ( disclaimer: i never used it, only is a example )

There is also bitcoinjs which is a fantastic and quick way to get hands on coding experience with bitcoin.

If you want to learn up, start here: https://www.npmjs.com/package/bitcoinjs-lib

MyDoge isn't open source, similar to major social media platforms. However, the wallet functionality is built on well-known, trusted open source libraries: https://github.com/bitcoinjs/bitcoinjs-lib https://github.com/novalabio/react-native-bip39 https://github.com/bitcoinjs/bip32 https://github.com/emeraldsanto/react-native-encrypted-storage

https://github.com/bitcoinjs/bitcoinjs-lib looks secure and reliable

The only interaction I had with that development team (at least I think it was that team) is that they were looking for a JS lib to do front-end transaction creation, and I pointed them to bitcoinjs-lib. Haven't heard anything after that.

I've created a Fog Of War map based on my data export using python in 30 minutes, and decided to build a web app to make it easier for others. Then I spent a whole day trying to figure out how to do it in JS, why it's way slower (https://github.com/Turfjs/turf/issues/2851), how to optimize it (I tried Rust wasm but had too many problems with bindings for geo), then trying to deploy it as a static page but had too many problems with next.js error pages and awaits.

This version is still alpha, doesn't collect your data, built with next.js and deployed to cloudflare pages like this https://developers.cloudflare.com/pages/framework-guides/nex...

to measure distances and convert between our parameters I'm using TurfJS, for which binding is even more trivial:

Turf.js is an open-source geospatial analysis library that can process various location data, such as the center of gravity and distance calculations.

Isochrones are manually calculated using turf.js assuming 1.2m/s walking speed after the subway trip. These are simple buffers around each station/prior isochrone and do not take the street network into account.

Not to take away from you learning, which I think is awesome, I was wondering if you know about http://turfjs.org/ which provides a lot of simple modules … and is surprisingly hard to find. Their `distance` modules may be relevant in this case.

you can use client side libraries like Turfjs to do buffers https://github.com/Turfjs/turf/tree/master/packages/turf-buffer

Tools: custom Javascript (with heavy use of turf.js) for data processing and creating the 3D model, Blender, 3D printing, lost wax casting

I've integrated https://turfjs.org/ with mapbox before and it was pretty fun