R

Looks like gitcoin could help fund continued development of beet too: https://gitcoin.co/grants/

There's now an open EOS grant to help fund continued BEET development: https://pomelo.io/grants/beetwallet

Is this still the case with the upgraded client? Or can we now close this issue?

We've now got this for the bitshares blockchain: https://github.com/bitshares/beet/blob/develop/src/lib/blockchains/BitShares.js#L155 I tried using the bitsharesjs node testing function, however it wasn't responsive enough https://github.com/bitshares/beet/blob/develop/src/lib/blockchains/BitShares.js#L199

Good to close this issue now :)

What about the following? https://about.signpath.io/product/open-source What I don't like about paid-for code signing certs is that it fully doxxes the cert owner, no whois protection, so something like the above...

Resolved in: https://github.com/beetapp/beeteos

I suppose you could use an on-chain asset's whitelist to keep track of scammers, there would be the associated asset update fees to account for however.

I've added this requested functionality for the transfer prompt: https://github.com/bitshares/beet/pull/189 There's other operations that we could warn about, like adding a blocked account to your beet wallet, perhaps some of...

Can close this issue now that the feature is implemented.