Back End capabilities.

1) So would it be possible for the contract to sign bitcoin transactions?
2) Is it possible for the contract to self execute in specified time?
3) How much data the contract could store in it's database?
4) Is it possible for the contract to open outgoing connections to other servers?
5) Will WEB3 applications be available in standart web browsers?

Comments

  • JasperJasper Eindhoven, the NetherlandsMember Posts: 514 ✭✭✭
    Good questions.
    1. No, contracts dont have private keys. They dont need to because they're fully defined by their behavior, and it "isnt possible" because their entire state is visible. SCIP might just be able to do it. (its weird)
    2. Contracts currently run when called. There might be and ALARM implemented later. Otherwise a CronDAO that people call and it calls lots of contracts that 'want an alarm'. Another solution is to just code in logic that time-evolves the contract as needed.
    3. As much as you can pay gas for. It is one of the more expensive things to do so! It is the scalability problem that all full nodes have to run and store everything. Lightweight clients use Merkle-tree -like mechanisms, but at some point the security of Ethereum as a whole starts to suffer. They're researching microchains, which afaik is a sort of merged mining, to try make it more scalable.
    4. No. Full nodes repeat all calculations, and if they have to talk to a server, they might get different responses. Basically, you need someone to use transactions to send this data in.(if you use such a server you're being trustful)
    5. Dont know, possibly not. There is some javascript version stuff, just maybe an addon.?.. Eris uses a local server which you can point your browser at, another option.
    This is sort-of an adoption struggle. Mozilla could for instance say, we'll put it in Firefox, yay! But the standard is a bit reliant on the people not being easily bended into following whatever hard fork. So, adding people 'by default' of their software is possibly not actually the most desirable thing. That said, DAO-ifying mozzilla too could provide more security that way :). Not very nice either if people use it through centralized servers, as Mt Gox illustrates.
Sign In or Register to comment.