4
Tezos doesn't provide any randomness though Michelson currently. PVSS features are expected to come in future proposals which can enable randomness generation.
Currently, the best solution is probably to use an oracle(decentralized or not) to achieve the necessary randomness.
2
When you add tezAmount liquidity you deposit tezAmount * tokenPool / xtzPool tokens (with division rounding up) and receive tezAmount * lqtTotal / xtzPool LQT (with division rounding down). When you remove lqtAmount liquidity you get back lqtAmount * xtzPool / lqtTotal tez and lqtAmount * tokenPool / lqtTotal tokens (with divisions rounding down).
2
You are correct. There is not a way to get the value directly. You would have to originate a contract like this. Let's call it getnat.tz. We will use it to create an error message after a dry run call.
parameter (nat);
storage unit;
code { CAR; FAILWITH };
Now we can call it from the client.
tezos-client transfer 0 from alice to token \
--...
2
You wouldn't get meaningful privacy. It would be the only asset in its own pool, so you would know every time it changes hands, which might as well be achieved by using fresh keys without any zero-knowledge proofs. The multiasset pool[1] would give you more meaningful privacy, but it's not a part of Edo.
[1] https://research.metastate.dev/multi-...
1
As far as I know, there aren't any. What you can do is copy the code of the token that interests you on Mainnet, deploy it on Carthagenet and create some tokens you can then use for your tests :)
Only top voted, non community-wiki answers of a minimum length are eligible