blog.ethereum-alarm-clock.com
The path towards an open market. — Ethereum Alarm Clock
http://blog.ethereum-alarm-clock.com/blog/2015/11/16/the-path-towards-an-open-market
The path towards an open market. November 16, 2015. As the Alarm service has evolved a few high level goals have formed with relation to the desired economics of the system. I'd like to spend some time sharing these, because they are important to understanding the motivations behind the technical implementation. The service should be an open market. The cost of scheduled execution should be cheap (. Ideally, negligible so that call scheduling can be pervasive. The execution of calls must be profitable.
blog.ethereum-alarm-clock.com
Available on the testnet — Ethereum Alarm Clock
http://blog.ethereum-alarm-clock.com/blog/2016/10/4/available-on-the-testnet
Available on the testnet. October 05, 2016. The contracts for 0.8.0 have been deployed to the testnet. Here are the relevant contract addresses. One of the easiest ways to start tinkering with this is going to be with the command line interface (CLI). Documentation for using the CLI can be found here in the Alarm Documentation. I'd like to specifically thank /r/johanngr. October 05, 2016.
blog.ethereum-alarm-clock.com
2,600 lines of solidity later... — Ethereum Alarm Clock
http://blog.ethereum-alarm-clock.com/blog/2016/9/29/2600-lines-of-solidity-later
2,600 lines of solidity later. September 30, 2016. Perfection is attained, not when there is nothing more to add, but when there is nothing more to take away.". So here I am, 2,600 lines of solidity later with an entirely rewritten Alarm service that I'm extremely excited about and I'd like to take a moment to point out a few of the cool new bits. Time and Block based scheduling. Libraries and more Libraries. And elsewhere where it is used. However, the magic of libraries doesn't stop there. With this si...
blog.ethereum-alarm-clock.com
v0.5.0 Deployed — Ethereum Alarm Clock
http://blog.ethereum-alarm-clock.com/blog/2015/11/9/v050-deployed
November 09, 2015. I've just finished up deployment and testing of the 0.5.0 release. Of the Ethereum Alarm Service. This release introduces a number of major API improvements that should make integrating with the service simpler and easier. This release marks a big step for the service. Moving the call execution into individual contracts opens up a much simpler path to new types of scheduled calls. The first that you are likely to see are calls set for specific times (rather than blocks), and th...
blog.ethereum-alarm-clock.com
A Dangerous Design Pattern — Ethereum Alarm Clock
http://blog.ethereum-alarm-clock.com/blog/2016/1/23/a-dangerous-design-pattern
A Dangerous Design Pattern. January 25, 2016. This issue has been addressed within the Oraclize it service but this post serves as a write-up on a design pattern that should be avoided by any service. The abstract solidity contract that Oraclize currently recommends using to integrate with the service exposes contracts to being drained of their entire account balance. This attack is possible because of two key components within the usingOraclize. This sets up a situation where your contract is allowing a...
blog.ethereum-alarm-clock.com
The Alarm service is now available on the Testnet — Ethereum Alarm Clock
http://blog.ethereum-alarm-clock.com/blog/2016/1/16/the-alarm-service-is-now-available-on-the-testnet
The Alarm service is now available on the Testnet. January 16, 2016. You can thank avsa. For pestering me to make the Alarm service available on the testnet. You'll find identical version of the service deployed onto the testnet @ 0xb8da699d7fb01289d4ef718a55c3174971092bef. I have a scheduling server hooked up to this instance of the alarm service so if you schedule a call there you can expect for it to get executed just the same as the main net. Reach out to me on gitter in the ethereum-alarm-clock.
blog.ethereum-alarm-clock.com
Running an execution scheduler — Ethereum Alarm Clock
http://blog.ethereum-alarm-clock.com/blog/2015/12/24/running-an-execution-scheduler
Running an execution scheduler. December 24, 2015. If you are interested in participating in the execution side of the Alarm service there is now documentation. To get you started. To help you test that your setup is working as expected there should be scheduled calls somewhere around every 1-2 hours for a few weeks while I try and help get people get their servers up and running and troubleshoot any issues they encounter. There are also two open issues ( #1. December 24, 2015.
blog.ethereum-alarm-clock.com
Introduction to the Python-Ethereum ecosystem — Ethereum Alarm Clock
http://blog.ethereum-alarm-clock.com/blog/2016/2/22/introduction-to-the-python-ethereum-ecosystem
Introduction to the Python-Ethereum ecosystem. February 22, 2016. Introduction to the Python-Ethereum ecosystem. This post is targeted at developers who are interested in getting started developing on Ethereum using python. Is python the right choice? It's important to know what you are planning to build because Python may not be the best choice for certain projects. Outside of the browser however, Python and Ethereum work very well together. Interacting with the blockchain. These two libraries provide a...
blog.ethereum-alarm-clock.com
Devcon1 and other musings — Ethereum Alarm Clock
http://blog.ethereum-alarm-clock.com/blog/2015/11/5/devcon1-and-other-musings
Devcon1 and other musings. November 05, 2015. Getting geared up to leave for London this Saturday to attend Devcon next week. It's been an amazing couple of months since the Frontier network went live. I'm looking forward to meetingthe people behind the screen names that I've been chatting with through various channels. Please feel free to seek me out during the conference. The best way to contact me during the conference is likely on twitter via @pipermerriam. November 05, 2015.
blog.ethereum-alarm-clock.com
v0.7.0 Deployed — Ethereum Alarm Clock
http://blog.ethereum-alarm-clock.com/blog/2016/1/30/v070-deployed
January 31, 2016. Version 7 of the Ethereum Alarm Clock service has just finished being deployed. Full source code for this release can be found on github. The latest documentation is available here. A new canary contract has been deployed to 0x24d76e09a1b82bfb7fdefa3fb0df1bab01e5b824. Full instructions on how to verify the deployed bytecode available here. Beta release of the scheduling client with compatibility with this new version of the service available on pypi. January 31, 2016.
