ethereum/solidity

The Solidity Contract-Oriented Programming Language - By chatting here you agree to the https://github.com/ethereum/solidity/blob/develop/CODE_OF_CONDUCT.md

jebuske

@jebuske

If I have ContractA is contractB, Pausable and I want to be able to call a function from contractB even when ContractA is paused. How should I do this? its inheriting from ContractB so I cannot add a modifier in contractA?

cryptodon15

@cryptodon15_twitter

Hey Guys any thoughts on this..... www.FluidAI.co

phalexo

@phalexo

@jebuske You are confused about what Pausable does. Particular methods with modifier whenNotPaused are made to revert in case pause == true. There is no such thing as pausing a contract.

jebuske

@jebuske

@phalexo Sorry, I maybe didnt explain myself correctly. So I have a contract ContractA is contractB, Pausable. When I change the pausedState of contractA to true I can no longer call the methods of contractB that it inherit because its in the paused state? I want to use the whenPaused modifier on these methods of contractB but I’m confused how this could be done

phalexo

@phalexo

As long as methods inherited from contractB do not have that modifier on them you can call them. You can also have two(2) Pausable contracts, i.e. PausableA and PausableB controlling methods of A and B separately. Have to use different names for modifiers and flags.

jebuske

@jebuske

@phalexo I’m afraid I dont understand how methods from ContractB can have a modifier from contractA on them? I guess thats what I’m trying to ask

I tried adding whenPaused in contractB but that doesnt work

Micky Socaci

@mickys

@jebuske ContractA is ContractB, Pausable, -> if you deploy contractA at 0x01, and then deploy ContractB to 0x0X, A will have the full code of B, and code changes that A does, but they do not share state / storage, you inherit / extend b's code

they're not linked inside the blockchain in any way

Uthai Rattanapacksopon

@calltong

0x8eb730425d44abb2f5f70f042c08c8214de4160c

beether

@beether

@mryellow yes, exactly

ive tried all sorts of things

Daniel

@DanielRX

Anyone have a suggestion for resources on sidechains for ethereum?

Julian Sauer

@notorious-clay

Simple question. I just can't find the result. address public kunde1 = 0xca35b7d915458ef540ade6068dfe2f44e8fa733c;

If I type it like that. It give me a waring. How can I do it right. So the kunde1 has a fix address.

thanks for the help

Daniel

@DanielRX

What is the warning...?

Julian Sauer

@notorious-clay

browser/Payment.sol:5:29: Warning: This looks like an address but has an invalid checksum. If this is not used as an address, please prepend '00'. Correct checksummed address: '0xca35b7d915458ef540ade6068dfe2f44e8fa733c.'

area

@area

pragma solidity ^0.4.21;
pragma experimental ABIEncoderV2;

contract NestedArrays {

    function test1(uint256[][3] u) returns (uint256 x){
        x = u[0][0] + u[1][0] + u[2][0];
    }

}

The above compiles, but I am unable to get it working correctly, either in remix or with a truffle test. When I run in remix, and pass something like [[1],[2,3],[4,5]] the transaction reverts and the 'decoded input' is very clearly wrong. A function declared with uint256[3][] works as expected, but that's not what I want (i.e. I want to pass an array containing three variable length arrays, not an array containing a variable number of arrays with length three). Is such a function parameter not properly supported, even though it compiles?

Jim McDonald

@mcdee

@notorious-clay Solidity expects addresses to conform to EIP-55 checksumming. In your case that address should be listed as 0xCA35b7d915458EF540aDe6068dFe2F44E8fa733c (note some upper-case letters)

@notorious-clay you might also want to consider updating your version of Solidity to one more recent, as it will show the correct error message and checksummed version of the address

Daniel

@DanielRX

@mcdee he did post the error message which listed the address but seems it failed to checksum it

(he used remix which may be why)

phalexo

@phalexo

Has ERC223 been accepted as a "standard"? Or is it still in the air? Thanks.

facundomedica

@facundomedica

Its status is "draft", it should be "accepted" to be a standard

Julian Sauer

@notorious-clay

thanks @mcdee

what is the latest version of solidity?

facundomedica

@facundomedica

@notorious-clay 0.4.21

https://ethereum.github.io/solc-bin/bin/list.json

ethernian

@ethernian

hello guys,
I have just constructed and successfully executed a token transfer transaction with extra data behind the message call (check extra 8888 added at the end of tx payload).
https://etherscan.io/tx/0xac41ca71ce075d7efb031433b205f99382cd63532de684b4437a23096b242c74

It seems working, but the question is: is it specified in solidity or it can change any time?
It is could be interesting as the base for stealth token transaction in ethereum

Daniel

@DanielRX

Is it possible for the bytecode for a contract to differ on etherchain and etherscan?

Jim McDonald

@mcdee

@DanielMReed possibly, if there are bugs in either website. Going to the chain direct is the only way to obtain bytecode without trusting a third party

Daniel

@DanielRX

@mcdee wanna take a look in /remix and see if you can work it out? I copied the etherchain source over and it just fails

phalexo

@phalexo

What would be the pitfalls of using ERC223 draft implementation at this time? Any thoughts? Thanks.

Jim McDonald

@mcdee

@phalexo i don't use remix so wouldn't know

Daniel

@DanielRX

It's an etherscan/etherchain issue I mean

Jim McDonald

@mcdee

@phalexo it's not a standard and there are enough competing (better) standards out there that at this stage it's unlikely to win mass adoption

phalexo

@phalexo

Thanks. Same question about other "standards" then, besides ERC20?

Jim McDonald

@mcdee

@phalexo they're all up in the air. My favourite is 777 but they're debating registry implementations at the moment (and honestly I'd prefer it if solidity devs could stop equating "not succeeding" with "reverting" as it would open new possibilities). If I had to build something today I'd build an ERC20 token with a separate token store and the ability to upgrade to another token standard when it's ready

@DanielMReed like I say, check out the bytecode on the blockchain and see which site matches

Daniel

@DanielRX

It's the verification that is failing, seems the bytecode is the same but the opcodes vary is all for that side

Jim McDonald

@mcdee

@DanielMReed Verification is very dependent on solidity version, optimisation and unfortunately bugs in the way that referenced code is imported. If you are pulling in any imports from outside of your immediate tree that might be part of the problem

phalexo

@phalexo

@mcdee The tricky part about upgrading one standard to another is what happens with data stored in state variables, and whether the storage structure changes. If a new standard 's changes are "orthogonal" to the old one it should be relatively easy.

Jim McDonald

@mcdee

@phalexo with most of the proposed standards the changes are orthogonal, yes. Anything that isn't you could plan for in advance if you think that it's at all a likely outcome.

In my ERC-20 contracts I have a separate storage contract for token balances but allowances are in the ERC-20 contract. If I upgrade to a contract without allowances (or without the same way of doing allowances) I can just drop the existing ones with the old contract and set something new up on the new contract. Plus, there's no reason why you couldn't leave the ERC-20 contract in place and have multiple contracts access the same token store

Daniel

@DanielRX

@mcdee See I know that, but none of those apply, the source is open, 0 imports, same version, same optim

Jim McDonald

@mcdee

@DanielMReed try compiling locally and checking the bytecode perhaps?

Jasvir Singh Grewal

@jasvir99

hi there. I was looking on qtum erc20 token and observed some strange addresses. https://etherscan.io/token/0x9a642d6b3368ddc662CA244bAdf32cDA716005BC#balances
can anyone please explain me, what are those?

Jim McDonald

@mcdee

@jasvir99 given that the contract doesn't list those as special cases I'd guess they were burn addresses (or programming mistakes)

Daniel

@DanielRX

Looks like burn (0x22222... 0x33333.... etc)

But aren't burns meant to transfer to 0x0?

Where communities thrive

People

Repo info

Activity