Denis Davidyuk

> How are those information secured, so the user can't be cheated by third parties in being shown some other information than intended? Wallets need to get an explanation from...

> the bytecode from the chain, no ACI and no source will be needed? to show messages, yes > an over-complication This can be really complicated to implement now, but...

consider implementing this algorithm: https://devchat.aeternity.com/group/aepp-sdk?msg=obZt9MS5QjZzzhPvN

Can be fixed partially by using endpoint from here https://github.com/aeternity/aeternity/issues/3662

Some time before I was investigating the ability to implement a custom wrapper around bigint to represent ae coints, but this feature on TS side is missed https://github.com/microsoft/TypeScript/issues/2361

Approximate roadmap (each step may be done separately): - [ ] don't use strings as numbers - [ ] use BigInt instead of BigNumber (drop BigNumber completely) - [ ]...

Optionally we can have a fancy way to define ae amounts ``` const aeAmount = ae`42.4`; const fee = aettos`19320000000000`; ``` Also, may be useful to define something between `ae`...

The first part I think is fixed in #1670. I missed the emitter interface when introduced printing of that error. > Unexpected message received Is there is a case when...

The idea is that sdk can be initialised with no accounts, nodes, compiler, but when one of SDK methods try evaluate one of these then exception would be thrown. So,...

```html SDK test in browser Open developer console const { AeSdkAepp, BrowserWindowMessageConnection, walletDetector } = Aeternity; const aeSdk = new AeSdkAepp({ name: 'aepp example' }); async function scanForWallets () {...