Recent changes will put the ledger of ether owned into a contract. Wallets are no longer a concept at the protocol layer (well, they are still used in mining).

Try out htmlbars or backbone

tried some things in vain, some docs would be nice

I tried to make each directory a set of templates, but so far it is creating weird bugs.

The bugs seem to care between other_function(functional_function()); and var a=functional_function(); other_function(a);, the former giving an error. Programming languages should in principle not care about that... The latter gives memory leaks issues..

Could do the same as with assets/...

Just like my other issue, probably low priority.

would replace the existing 'transactions' section

I'm trying to get the sub-currency example from the whitepaper to work and it never runs the contract (storage is never updated), it just accumulates credits from the incoming transactions. There is no indication as to what is failing. It's possible it's a syntax error - I've attempted to adapt the CLL from the whitepaper into JS for the simulator. Here is what I'm submitting as the contract code:

if (tx.value < 100 * block.basefee) {
    return
} else if (contract.storage[1000]) {
    var from = tx.sender
    var to = tx.data[0]
    var value = tx.data[1]
    if (to <= 1000){
        return
    }
    if (contract.storage[from] < value){
        return
    }
    contract.storage[from] = contract.storage[from] - value
    contract.storage[to] = contract.storage[to] + value
} else {
    contract.storage[MYCREATOR] = 10^18
    contract.storage[1000] = 1
}

Both for the readme and for landing-page of the simulator

MIT makes most sense

Trying to run the hedge example fails. It seems to be on the block.contract_storage() line, which raises an Uncaught Reference Error "sim is not defined."

modify existing contracts storage, etc

why not. play god.

🚮

These would be nice. Perhaps most flexible is to do eventResponse[stringify(event)](enough_state_to_change), and simply have an dictionary of functions as response.

One thing i would like is to be able to use the arrow buttons to navigate between stuff. But i am not sure how to implement that without making things more complicated than they should be.

so we can actually calculate crypto fuel burn, and run real contract code

An escrow contract that accepts funding from many donors. Funding is forwarded to the author if the funding goal is met before the deadline, otherwise all funds are returned to the backers.

State change triggers:

• Funding goal (account balance)
• Funding deadline (time)

Data storage:

• Funder address + amount

Outcomes:

• All money goes to author
• All money goes to funders

You could have a 'simulation mode' where you take out the block mechanism and replace it with a 'fake compliant' one.

Ethereum scripts, fees would automatically work the same as in ethereum because it essentially is ethereum.

for introducing the topic of a crypto contract

need to write a cll -> js transpiler

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with greenkeeper/.

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

Once you have installed CI on this repository, you’ll need to re-trigger Greenkeeper’s initial Pull Request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper integration’s white list on Github. You'll find this list on your repo or organiszation’s settings page, under Installed GitHub Apps.

Would it be possible to get a trace of the code execution as part of the output?
I'm imagining source line (with line number) on the left and corresponding evaluation and result on the right.