What is this adminRole supposed to be? An address? Or a hashed value of something? What is it?

Check it out on this page: https://github.com/OpenZeppelin/openzeppelin-contracts/blob/master/contracts/utils/structs/EnumerableMap.sol

create2 is not necessarily a real deployment. It first calculates the address if it were deployed, as far as I know.

Nope..I believe its a new opcode that is specifically designed to deploy new contract.

Estimating contract address is just one of its effective features.

it can predict an address as well as do a deployment. What makes create2 outstanding is something called counterfactual deployment.

I have the same understanding, this new opcode should deploy contract always to the same address (as long as the bytecode and salt do not change). the deployment is successful but I do not see the tab where to verify the contract and also an automated request to etherscan api does not work

It means one can get the address first without doing a deployment. Of course, a contract can be later deployed to that address.

some docs about this?

https://docs.openzeppelin.com/cli/2.8/deploying-with-create2

merci

Guys Events cost gas fees right?

So if I have an array is better to emit once the cicle is ended

thanks

According to the AccessControl contracts of OpenZeppelin...
Tge AdminRole or another role is a keccak256 hash

cryptozombies

Well, if it's a bytes32 viable, it's most likely a hashed value. The question is a hashed value of what? Address? A string?

reflective finance

bot?

A custom String

Like I define a role as "MANAGER" and create a hash of it

and check weather the caller has this role assigned or not

So how to prevent price dumping once provided liquidity for your own token

Is there a way to calculate slippage for a token?

I'm not quite sure of the calculation, but watch that video it explains it to some extent but not in detail. Slippage is mentioend e.g. on Pancake Swap or Uniswap when you do the trade under price impact

and of course the speed of your transaction going in is part of the slippage too.. if someone moves the price before you get in you need to have slippage set to allow for that trade to execute, or as a safety net it will not if you do not allow sufficient slippage.

yes I know also that slippage is higher for lower liquidity right?

It depends on how much you are swapping

its a function of the amount you are trying to swap vs the liquidity that exists in the pool.

maybe this sheet can help

did a link come through?

does this chat remove links or something?

I don't knoe
but you can try posting without dots

docs google com/spreadsheets/d/1tfNoKooe66Jz5ltA-vEmE3f6EKCpLmNI1uBDwf5wHII/edit#gid=0

merci

np.

Np, thanks same to you

oh, ok... will be better tomorrow then heh

))

Are you sure?

struct RoleData {
mapping (address => bool) members;
bytes32 adminRole;
}

mapping (bytes32 => RoleData) private _roles;

bytes32 public constant DEFAULT_ADMIN_ROLE = 0x00;

The bytes32 in the mapping(bytes32 => RoleData) is what you described for sure. I'm not sure about adminRole. It would be redundant if it were for a hashed value of a ROLE string.