Here's my updated DAO code that should compile fine for v0.4.16 of the compiler: https://github.com/MidnightLightning/ethereum-org/blob/6b9f4b281a6efd80d1fb9aa7e1b2f912123d89b1/views/content/dao.md
Currently I am trying POA tutorials on parity wiki
Hello to all...
i think that there is a problem with the "create your own crypto-currency" tutorial here
https://www.ethereum.org/token#full-coin-code
I try to explain what i think.
The contract tokenRecipient is an abstract contract right? (if i'm wrong explain that please)
So there are two questions:
1) why the tokenRecipient contract is not inherited from another contract in the tutorial?
2) why in the function approveAndCall inside the "token" contract there is this line of code "tokenRecipient spender = tokenRecipient(_spender);" ?
I mean, if tokenRecipient is an abstract contract should not be used like that.
@AyushyaChitransh Parity is a node client for Ethereum, which does the same job as Geth. I installed mine as a Docker container since that keeps it really compartmentalized, and then start the server using the
chain --dev flag to starting private development mode, and navigate to the web UI to push contracts and interact with them in development mode. Have you tried that and gotten stuck at some point in that process?
@lucav The line
tokenRecipient spender = tokenRecipient(_spender); means "take the _spender variable (which is an address value that the transaction sender input) and cast it to a tokenRecipient contract class (meaning, assume that whatever destination address the user is wanting me to use, assume that it meets the interface defined as tokenRecipient)" That make sense?
So, for that sample token, if you just want to give another contract some allowance from your stash, you use
approve. If the other contract you're giving an allowance to is another smart contract, and it has implemented a receiveApproval function (to let it do some logic immediately after receiving some tokens), use the approveAndCall function to trigger that all in the same transaction call.
@MidnightLightning
When a contract is defined in Solidity like the
tokenRecipientone in that contract, it acts kind of like what an "interface" would be in other languages.
Ok, but i'm confusing...so in that tutorial, should be corrected from
contract tokenRecipient { function receiveApproval(address from, uint256 value, address token, bytes extraData); }to
interface tokenRecipient { function receiveApproval(address from, uint256 value, address token, bytes extraData); }right ???
thanks for your help
(i'm using that documentation as reference http://solidity.readthedocs.io/en/v0.4.15/contracts.html#interfaces )
To use, you deploy that whole Solidity script. It has definitions for several contract types, but when deploying only one becomes the main logic for the deployed address. All the other contract definitions in the script are supplemental/reference for the main contact
Oh actually, looking at that documentation, they did add in the "interface" keyword, my bad!
@MidnightLightning
Anyway, with contract keyword it works.
But for complete understanding the tutorial, i need to know this:
Should i deploy only the MyAdvancedToken contract (using truffle)?
Should i call the deployer link also or i don't to link?
This is my migration code:
var owned = artifacts.require("Owned");
var Token = artifacts.require("Token");
var TestCoin = artifacts.require("TestCoin");
module.exports = function(deployer) {
deployer.deploy(owned);
deployer.deploy(Token,1000000,'TestCoin',0,'TEC');
deployer.link(Token, TestCoin);
deployer.link(owned, TestCoin);
deployer.deploy(TestCoin);
};Thank you very much for help me!
I haven't used the Truffle infrastructure much at all, but you should only need to deploy the one
MyAdvancedToken contract for basic functionality. If you want to test the approveAndCall functionality, you'd need to deploy a second contract that implements that one receiveApproval method.
Hey I need to get one thing straight. Please someone help me . I am confused with this stuff. I want to create a commercial coin on ethereum network. There are 3 pages of tutorial on ethereum.org . I successfully implemented the first one. Now, what do I need to do? how and where to put it on so that people can trade ?
will I be able to create full coin that people can invest in?
Hi, I'm trying to set up my first digital token using the tutorial. However, when I cut and paste the provided code into the Solidarity Contract Source code text field, I get the following error:
Source file does not specify required compiler version!Consider adding "pragma solidity ^0.4.11
contract MyToken {
^
Spanning multiple lines.
Source file does not specify required compiler version!Consider adding "pragma solidity ^0.4.11
contract MyToken {
^
Spanning multiple lines.
does someone have the Full coin code?
Ah. Well, you could use the online Remix tool to compile the contract for you: https://ethereum.github.io/browser-solidity, or you can switch the version indicated in the
pragma command to be the version you have.
is there any coin created this way ?
Hello Everyone. I have a problematic wallet contracted that I created using Mist. The wallet is showing a positive balance inside Mist, and on Etherchain and Etherscan. When I try send funds from this wallet address to any other I get an error that says "Unknown Account". I know the password is correct. Interestingly, whenver I search for this wallet on Etherchain/Ethercan I can see the address and the balance, but then the browser tab completely locks up. I've tried everything I can think of. Has anyone else heard of this problem? Do you have any suggestions?
I have an issue following the instructions for remix for deploying your first contract. https://medium.com/@jamesray_56543/unfortunately-i-dont-see-any-of-this-d87ca724a22a.
ethereum/solidity#2867
@blacksausage it seems that Mist isn't really ready for use yet, best to wait until it is usable with later releases that aren't pre-releases.
@blacksausage It does not look by your post that you have actually put any ether into that Wallet. If you used Ethereumwallet to create that wallet contract and you've synchronized with the blockchain, perhaps it is a collision, i.e. you have stumbled into someone else's wallet. I don't know what the odds are for two different sets of keys to generate the same address, but it sounds interesting if it did happen.
can somebody guide me