Return to Answer

By chance I was looking at the following transaction 0xfb2d580342988f20c9bd4b756555d6139f55ab2e5df2c5f99886c6195221faee in my answer to What is the address and balance of The DAO's extraBalance account:

By chance I was looking at the following transaction 0xfb2d580342988f20c9bd4b756555d6139f55ab2e5df2c5f99886c6195221faee in my answer to What is the address and balance of The DAO's extraBalance account:

Example Of createTokenProxy() Usage

By chance I was looking at the following transaction 0xfb2d580342988f20c9bd4b756555d6139f55ab2e5df2c5f99886c6195221faee in my answer to What is the address and balance of The DAO's extraBalance account:

The transaction is from the Poloniex wallet and includes the extra data 0xbaac530000000000000000000000000003f59b7e25819a64fc2f7199e89457593fe3500d.

I entered the following command in geth to find that the first 4 bytes of the sha3() of the function createTokenProxy() matches the first part of the extra data, which is how functions are called in transactions.

> web3.sha3('createTokenProxy(address)').substr(0, 10) "0xbaac5300" 

Poloniex is using this function call when individuals purchase The DAO tokens via the Poloniex - Create DAO Token screen.

It's not extra data that is sent with the transaction, but a call to the function createTokenProxy() with the DAO's address that has probably created the extra 110 tokens.

As noted by @Tjaden, the extra data that is sent with the transaction is a call to the function createTokenProxy() with the DAO's address that has probably created the extra 110 tokens.