Following
https://web3js.readthedocs.io/en/v1.3.0/web3-utils.html?highlight=BN#bn

Run:
new BN('0xea').toString();

Expected behavior

"234"

Actual behavior

"3450"

PS: web3.utils.toBN('0xea') returns "234" correctly

this will very quickly get out of hand if we allow it, i realize we don't have principles written down anywhere but to date one of them has been that binaries 'just work' without having to do any configuration. currently a user must set FN_MAX_REQUEST_SIZE, FN_MAX_RESPONSE_SIZE -- neither of these should be required to run.

test case:

cd tests/fn-system-tests/
go test -v

this

Reliability monitoring - e2e testing of GitHub workflow

Context

Since moving the Communtity Cluster from GKE to DigitalOcean the reliability has dropped dramatically due to issues with the Cilium networking driver 1.4.0. A separate action will be required for this, but in the meantime it highlights a lack of e2e monito

TODO: write up user story for this feature

This came up while reviewing #1734, adding Expires to de Digest method of pss/message.Message would work towards achieving this.

Why are you submitting this feature request
Accounts are not currently protected in the event of the password database becoming public, or if the individual account holder has their password compromised.

Describe the solution you'd like
Yubikey support.

Describe alternatives you've considered
Please don't use SMS.

Additional context
The account is worth protecting. It