20 BTC bounty for first AT *atomic cross-chain transfer* with Script clone

[CIYAM]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

To win: Be the first Script (i.e. Bitcoin or Litecoin) clone to implement a *working version* of AT on mainnet which will be used to
perform a successful "atomic cross chain transfer" with Qora (which will be implementing AT soon).

This will need to be performed within 1 month of Qora going live with AT (and if that doesn't happen within 3 months then
this bounty will be called off).

Bounty Address: https://blockchain.info/address/1AKRYi1Q2LtEAnEYzjjZXkZRXL33RKA53e (this address is kept in cold storage)

I created AT (http://ciyam.org/at) in order to allow any blockchain to have "Turing complete" txs easily added and it will soon be appearing
on some non-Bitcoin based blockchains, however, one of the *killer apps* for AT (atomic cross-chain transfer - at least IMO) really needs to
work with Bitcoin/Litecoin clones as soon as possible (and down the track there might be bounties offered for other blockchain variations).

I am not really concerned if the coin is *popular* (use of some low value coin is okay as long as the network is stable enough to achieve the
desrired result) but it must be using its *mainnet* and it must successfully accomplish an "atomic cross chain transfer" between itself and Qora
using AT.

In order to help *get the ball rolling* I've already outlined a fairly simple approach that could be used to get AT working from Script
(http://ciyam.org/at/at_script.html) and I will offer my personal assistance (with technical questions) free of charge (assuming I have
the available time).

Note that the code for the AT and AT API implementation must be "open source" using the MIT license (even if the rest of the code is not) and the final
say over whether the result to collect the bounty has been achieved will be up to myself.

If others want to add to this bounty then please send your BTC donation to the above address (note the following signed message to prove
that I own it and the GPG sig for this announcement).

1AKRYi1Q2LtEAnEYzjjZXkZRXL33RKA53e
This address is under my control!
G3YRn7DmQF0Jf5nBaJiw3SfMVroQzFB4N6X1AmNGmUYEaTCbfTOoZExiE2qAqHLdnA4IgIx+D+ccwVsjF3CWCuI=


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)

iEYEARECAAYFAlRk4YIACgkQZPzMrvJlEZATTgCghPw1X2sGRbXLxOlObggxjn2/
vFQAnj/xMMk5pXr1kXOJB8HfkGOEUCPL
=73Pq
-----END PGP SIGNATURE-----

[1714077779]

1714077779

[1714077779]

1714077779

[1714077779]

1714077779

[1714077779]

1714077779

[CIYAM]

I reformatted the OP and made it clear that at least the AT and AT API part must be open source and that my judgement is final but I won't be changing it much again (so the *rules won't be changed from this point on*) apart from to fix any typos or clarify anything that is ambiguous.

[CIYAM]

Note that this bounty is going to be added to (by myself if no-one else) as I am very keen to see this happen.

I have already been contacted by a few interested devs so those *waiting for the bounty to increase* might want to at least "get in contact" so they will still have a "chance at the bounty".

In any case *everybody wins* if AT appears on multiple chains as it means all those blockchains will be able to do things like "lotteries" and "auctions" as well as "atomic cross-chain transactions".

[rlh]

I sooo want to go for this, but I don't think I have the time to start a project yet.

I've not dug into the AT code (yet), are Nxt-to-Qora transactions as plausible as btc-to-qora AT transactions?  I had an idea for an asset based project and this could help me immensely.

Hmm... The wheels in my head are rolling...

[CIYAM]

Yes Nxt-to-Qora would of course be possible (assuming Nxt AT goes to *mainnet*) but understand that the bounty itself is only being offered for a Qora to a Bitcoin/Litecoin clone succeeding in performing an atomic cross-chain transfer/transaction via AT between them (as Qora have said they will take AT to *mainnet* first and I then want to see a "mainnet" version of a Bitcoin/Litecoin clone also).

Keeps those wheels in your head rolling - there are likely to be more bounties down the track!

[GrandpasNaked]

Dzimbeck and BitHalo have something like that for release soon. you should tweet this to him 

[CIYAM]

Dzimbeck and BitHalo have something like that for release soon. you should tweet this to him 

Sorry I don't use Twitter but feel free to do so yourself.

[SuperClam]

Should go without saying, but on a sad note:
You may want to specify 'open source'.
There seems to be a disgraceful movement towards closed source in some communities.
Regardless, you hold the strings to the purse (and the ultimate decision) but I thought it might bear mentioning.

[sparta_cuss]

Should go without saying, but on a sad note:
You may want to specify 'open source'.
There seems to be a disgraceful movement towards closed source in some communities.
Regardless, you hold the strings to the purse (and the ultimate decision) but I thought it might bear mentioning.

Right now Qora is closed source. Of course it will have to be open to Ian in order for him to do the Qora AT work, but I wouldn't assume he'd be against closed source. Ian, what do you say?

[Vrontis]

Should go without saying, but on a sad note:
You may want to specify 'open source'.
There seems to be a disgraceful movement towards closed source in some communities.
Regardless, you hold the strings to the purse (and the ultimate decision) but I thought it might bear mentioning.

Right now Qora is closed source. Of course it will have to be open to Ian in order for him to do the Qora AT work, but I wouldn't assume he'd be against closed source. Ian, what do you say?

If close source projects want to use AT that is of no concern to me (license is MIT not GNU).

If they make their version of AT *incompatible* with others then it would basically just either make it harder or maybe even impossible for that blockchain to participate in atomic cross-chain transfers (which wouldn't be likely to help with making their blockchain very popular).

[CIYAM]

I did state that I have the final decision and if I am unable to "see" the Script implementation (for the purposes of getting AT to work on other blockchains) then I would not be very happy.

I don't care if the majority of the coin is "closed-source" but I would be asking for the AT part (at least the Script changes) to be made public so that other blockchains can use AT.

As a general rule I don't support "closed source" and AT itself will always remain open but I am not going to dictate to others what to do with their source code.

[CIYAM]

I have clarified that the AT and AT API implementation must be open source (the rest of the platform is not my concern) and I will be publishing an AT API specification document at the end of the week.

The "atomic cross-chain transfer" AT itself will be coded by myself and will simply require that the blockchain platform correctly implements AT and the "generic fuctions" for the AT API.

When I publish the AT API I am going to "up the bounty" so those interested might want to "get cracking real soon".

Let's see if we can get an atomic cross-chain transfer to occur between to different blockchain mainnets before the end of the year.

[CIYAM]

So the AT API document is nearly complete (just getting some final reviewing).

Again - the bounty will be increased once I release the docco (in the next 24 hours) so those interested should be *watching this space*.

With the announcement of *side-chains* from Adam Beck and others I would guess a lot of alts now need to seriously consider their future. AT will give them a reason to exist (if they weren't just created for the purpose of *pumping and dumping*) with the ability to to "atomic cross-chain transfers" to other alts.

This is *evolution* at work!

[abramovich]

Sorry I don't use Twitter but feel free to do so yourself.

well it is not needed

[criptix]

Hi ciyam,

i think this project should interest you.

Atomic is developing a method for cross-blockchain transactions without the need of changing code for the respected coins.

/edit

sorry, didnt meant to hijack your thread for advertisment
i though it was related to your OP
if you have time you should read the documentation, there will be several steps to secure the system is trustless.

[CIYAM]

@criptix - it really isn't very polite to post an "ad" in someone else's topic (your sig is noted).

And something that relies upon "gateways" is in no way *trustless* so we are not talking "apples and apples" here.

[CIYAM]

Bounty has been upped to 10 BTC and the AT API document has now been released: http://ciyam.org/at/at_api.html.

Work on creating the actual atomic cross-chain transfer AT has already begun (see next post) and will be completed after the API has been thoroughly reviewed and tested.

Devs should note that the four use cases documented do not use the portable functions listed in the AT API (those use "experimental" functions and should only be considered as illustrative examples for writing ATs).

[CIYAM]

In order to show clear progress of the atomic cross-chain transfer AT itself (and to ensure that no-one has any unfair advantage) I will be posting pieces of the machine code as it as being developed.

So here is the first portion which does the all important "refund" if too much time has elapsed (note that the @refund_minutes value would be part of the "initial data" when the AT is created):

Code:

Variables
--------
@00 ==> @refund_minutes
@01 ==> @refund_timestamp
@02 ==> @current_timestamp

Script Assembly
---------------
if @refund_timestamp not zero goto loop                  1e010000001c
set @refund_timestamp to AT creation time                35010301000000
add @refund_minutes to @refund_timestamp                 370604010000000100000000000000

:loop (0x1c)
set @current_timestamp to block timestamp                35000302000000
if @current_timestamp >= @refund_timestamp goto refund   2102000000010000002d

(add NOP padding to insert code later) 7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f

:refund (0x50)
set B to address of the AT creator                       320b03
send remaining balance to address in B                   320304

Assembly Code
-------------
00000000* BNZ $00000001 :0000001c
00000006  FUN @00000001 0x0301
0000000d  FUN @00000001 0x0406 $00000001 $00000000
0000001c  FUN @00000002 0x0300
00000023  BGE $00000002 $00000001 :00000050
0000002d  NOP
00000050  FUN 0x030b
00000053  FUN 0x0403

Machine Code
------------
1e010000001c35010301000000370604010000000100000000000000350003020000002102000000010000002d7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f7f320b03320304

[HostFat]

I've put this on Reddit:
https://www.reddit.com/r/Bitcoin/comments/2kf579/10_btc_bounty_for_first_at_atomic_crosschain/

[maaku]

You can do atomic trade with regular old bitcoin script. Would that qualify for this bounty?