Liam Zebedee
Liam Zebedee
Um. Is this ever eventuating? I was very surprised to learn this isn't part of the API.
> @johnmee this wouldn't be much different from, say, the PayPal API to send money, or any other type of "destructive" APIs. The user of the API is obviously responsible...
`std::stark would be nice to add this for recursive STARK verification - but this might be quite ambitious.` Would love to see this @bobbinth.
For reference, the stack trace looked like: ``` Traceback (most recent call last): File "/usr/local/lib/python3.5/dist-packages/pycoin-0.70-py3.5.egg/pycoin/encoding.py", line 75, in to_long v += lookup_f(c) File "/usr/local/lib/python3.5/dist-packages/pycoin-0.70-py3.5.egg/pycoin/encoding.py", line 141, in v, prefix =...
I think the term here is data availability attack @gakonst and it's a good point. Did some deeper research today (some more links above) - the preimage/submarine approach should work...
This is so crazy, it might just work. Had some time to brew over this: - obviously this introduces a dependency loop in the design, which rings a couple bells....
> it's a supply peg, not a price peg Those magic words - this is the essence of it. Let's do it!
A naïve question - what drives liquidity for these auctions? With a trusted price feed, we are assuming some vested interest from those maintaining it. What makes this ETHBTC market...
I mean, I did my homework ;) @mhluongo
https://ethereum.stackexchange.com/questions/32354/mapping-to-contract You're bringing the whole bytecode of MyContract into MappingExample. The code for MyContract isn't shown, but let's say it's near the gasLimit because it's a complex beast. MappingExample will...