The Solidity Contract-Oriented Programming Language - By chatting here you agree to the https://github.com/ethereum/solidity/blob/develop/CODE_OF_CONDUCT.md
Hey wonderful Solidity devs. Hope you're having a great weekend. I've personally been spending my weekend pulling out my hair writing solidity code that can interface with 0x Protocol to do price discovery. If anyone has any advice, would be much appreciated. Here's a full breakdown of the problem if you feel charitable and brilliant today https://gitcoin.co/issue/ProofSuite/OrFeedSmartContracts/10/3748 . There's a bounty too if you're no feeling charitable, but capitalistic and brilliant.
And now I'll go back to being disappointed and sad, especially as one of the many issues surrounding this seems to come from the fact that you can return structs in solidity, but clients that you might test a contracts response on (Etherscan contract reader etc) can't support that because web3 doesn't support that, giving weird tuples dont work response... or something like that.
aliatiia (haven't found anything in the solidity docs but I am asking here to make sure I didn't just miss it)
all it cares about is processing a transaction and other managerial duties such as consensus
so I don't think you have any visibility to anything outside your current transaction scope
at least can't think of any such data
anyway, here's all of it, I guess you already went through the list: https://solidity.readthedocs.io/en/v0.5.12/units-and-global-variables.html#special-variables-and-functions
According to this thread, https://ethereum.stackexchange.com/questions/36229/invalid-solidity-type-tuple, the new web3 supports tuple responses from smart contract. Not sure why Etherscan has not integrated it... Any one have suggestions on a better smart contract interface (GUI) that uses the latest. Remix is good for contracts you're writing, but I mean for other's contracts/reading/writing to them?
constructor(uint _totSupply, string memory _tokenName, string memory _tokenSymbol, string memory _voteName, string memory _voteDesc, uint _startDate, uint _endDate, bytes32[] memory _nameOption, bytes32[] memory _descOption
) public {
owner = msg.sender;
totalSupply = _totSupply * 10 ** uint(0);
balances[owner] = totalSupply;
tokenName = _tokenName;
tokenSymbol = _tokenSymbol;
vote.voteName = _voteName;
vote.voteDesc = _voteDesc;
vote.startDate = _startDate;
vote.endDate = _endDate;
from constructor of course
and i prefer ethers
but i have a wrapper, which makes contract deployment and interaction easier
you can't "hold" transactions which are sent to the blockchain
Knuckle Noise Hello everyone, do any of you know of a list of blockchain projects that use Solidity? I don't mean tokens like BAT or ENJ, etc. but blockchains where you can create smart contracts with Solidity. Like Ethereum, Tron, ThunderCore, etc. Are there more projects in this direction?
This is the very first deploy on mainnet https://etherscan.io/vmtrace?txhash=0x6c929e1c3d860ee225d7f3a7addf9e3f740603d243260536dfa2f3cf02b51de4
Wondering what the purpose of that SLOAD at the 6th instruction is?
[We're trying to optimize state accesses for Geth, and this SLOAD really bothers me as it skews my metrics, trying to figure out what it is]
@karalabe ah! Yeah, this is gavin's great suggestion to pack multiple elements in a single storage slot to save gas
so you of course have to first read the slot and then or the new stuff in
the problem is that it is rather tricky to determine if there actually is anything else in the slot or not
contract Version1 {
address owner;
}
contract Version2 {
address owner;
bool disabled;
}
If we enable this optimization, then code that works on version 1 might just use a plain sstore, while code working on version2 needs sload+sstore.
Of course, if all the code is updated in one run, then this is fine, but I'm still not very sure we should do this.
@xxs-Heung did you try any of the nightly development builds?
Can you anyone help ?
I have a doubt
I have a doubt