Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Piotr Kosiński
    @kosecki123
    estimation returns 1gwei but for some reason it still uses tx.gasPrice
    Joseph Reed
    @ChicoBitcoinJoe
    ya just saw that
    Piotr Kosiński
    @kosecki123
    The logs you sent me, they are not from the updated timenode
    Joseph Reed
    @ChicoBitcoinJoe
    not sure why that would be. I installed the cli using npm i -g @ethereum-alarm-clock/cli. Then i checked the version and it was correct
    I even removed it before
    Looks like we didn’t update the npm, the lastest should be 4.1.1
    Joseph Reed
    @ChicoBitcoinJoe
    sweet! I'll try it
    Piotr Kosiński
    @kosecki123
    released now
    ➜ npm info @ethereum-alarm-clock/cli
    
    @ethereum-alarm-clock/cli@4.1.1 | MIT | deps: 18 | versions: 34
    Command-line tool written in JavaScript to interact with the Ethereum Alarm Clock
    https://github.com/ethereum-alarm-clock/eac.js-cli#readme
    
    keywords: ethereum, smart-contracts, ethereum-alarm-clock
    
    bin: eac
    
    dist
    .tarball: https://registry.npmjs.org/@ethereum-alarm-clock/cli/-/cli-4.1.1.tgz
    .shasum: 1534d71584df25488fe2cd0e26354ae7b0b470ac
    .integrity: sha512-y8H9qGcDmzGBhBCGZ5/GoPBGmvzUPNLVZfXxUMooeQiBJLWHnMvII8QQom2Len4kYU5LebNugg0HTC/M5D0YDA==
    .unpackedSize: 60.8 kB
    
    dependencies:
    @ethereum-alarm-clock/lib: 0.1.0           cli-table2: 0.2.0                          keen-tracking: 4.0.7                       web3-providers-ws: 1.0.0-beta.37           
    @ethereum-alarm-clock/timenode-core: 6.2.0 commander: 2.19.0                          lokijs: 1.5.6                              web3: 1.0.0-beta.37                        
    bignumber.js: 5.0.0                        console.table: 0.10.0                      moment: 2.23.0                             websocket: 1.0.28                          
    bluebird: 3.5.3                            dotenv: 6.2.0                              ora: 3.0.0                                 
    clear: 0.1.0                               ethereumjs-util: 6.0.0                     readline-sync: 1.4.9                       
    
    maintainers:
    - adibas03 <adibas03@ymail.com>
    - chronologic <team@chronologic.network>
    - pkosin <pkosin@protonmail.com>
    
    dist-tags:
    latest: 4.1.1  
    
    published 33 seconds ago by pkosin <pkosin@protonmail.com>
    Joseph Reed
    @ChicoBitcoinJoe
    excellent
    Joseph Reed
    @ChicoBitcoinJoe
    It looks like my alarms are underfunded atm but the new logs look like the everything is working correctly
    Piotr Kosiński
    @kosecki123
    This contains the explanation on how to calculate the maxGasPrice
    Joseph Reed
    @ChicoBitcoinJoe
    I set my deposit to 10% higher than the gas cost but that isn't covering the expenses.
    Can .times(arbitraryCoefficient) be greater than 1?
    Piotr Kosiński
    @kosecki123
    nope this is 1 at max
    1 is the ideal situation, where gas price has not changed between claim and execute
    Joseph Reed
    @ChicoBitcoinJoe
    my claim cost is always zero
    oh wait nvm, that is what I'm missing
    my claim deposit is zero. Terminology mishap lol
    If the tx is never claimed than claimCost would be zero right?
    Piotr Kosiński
    @kosecki123
    yes
    well, no, the timenode will always claim that
    the cost will be the same,
    the difference is that, the chance for the execution is lower without the deposit
    (in case claiming node not execued in his window)
    in that case deposit is an extra incentive for other nodes to execute on the expense of the failing node
    you should set it
    wallets by default set required deposit = bounty
    Joseph Reed
    @ChicoBitcoinJoe
    What about the use case where the bounty is set at claiming?
    Joseph Reed
    @ChicoBitcoinJoe
    I'm not sure the EAC design is well fit for funding an alarm at the time of execution since it's design is built around funding at the time of creation. I'll keep thinking on this though.
    manihagh
    @manihagh
    @kosecki123, the code in tutorial to schedule transaction now throwing this: (node:95827) UnhandledPromiseRejectionWarning: Error: Returned values aren't valid, did it run Out of Gas?
    at ABICoder.decodeParameters (/Users/mani/Work/EWF/alarm-clock/schedule-project/node_modules/web3/node_modules/web3-eth-abi/src/index.js:226:15)
    And it was great to have a tutorial to cover up to transaction claim confirmation on the timenode
    Piotr Kosiński
    @kosecki123
    Thanks, I guess it’s not updated to latest migration to web1.0 which turns to be pain in the ass :)
    Will gonna take a look at it and fix.
    manihagh
    @manihagh
    Thats great, thanks for the reply.
    I have a question. How does the eac.schedule({ knows the deployed EAC contract addresses ?
    Piotr Kosiński
    @kosecki123
    So the lib npm package hold all addresses and abis for known networks
    then based on provider networkId we are chosing the correct addresses
    Joseph Reed
    @ChicoBitcoinJoe
    Is there a reason the smart gas estimation is not on by default?
    Joseph Reed
    @ChicoBitcoinJoe
    The "dumb" nodes will claim my alarms and then attempt to execute them with 0 gas still. I took your recommendation and set the claim deposit to the bounty. For some reason my node wont execute after the claim window so not sure what is happening there either.
    Joseph Reed
    @ChicoBitcoinJoe
    Updated the dapp to work with the smart gas estimation: https://everchain-project.github.io/recurring-transactions/
    My node is offline atm so start yours with it enabled if you want to expirement with the dapp. I've been having trouble keeping my node synced. Do you run your own node? The infura websocket provider no longer works with the timenode unfortunately.
    Piotr Kosiński
    @kosecki123
    Yes, we do have QuikNode fullnode that we use, you can also try with light client setup using Geth.
    manihagh
    @manihagh
    Are there any punishments for time-nodes claiming transactions but fail to execute for consecutive times ?
    Piotr Kosiński
    @kosecki123
    The punishment is that they will lose the deposit evety time they miss the execution
    There is no rankings or such for that matter
    Daniel Honerkamp
    @DHonerkamp_twitter
    Hi, I'm trying to include a scheduled call in one of my contracts. Might be a silly question, but how would I create the callData field if I want to also pass an argument to it ? (E.g. to call a function myFunction(uint256 _input1) with the argument _input1=10? I know that without an input argument I would create it with bytes4(keccak256("__myFunction()"))
    Piotr Kosiński
    @kosecki123

    Hey, you need to encode the method signature and parameters into ‘callData’

    Take a look a this thread on so it explains how to do it, EAC uses the same encoding as regular ETH transaction.

    https://ethereum.stackexchange.com/questions/3364/encoding-decoding-contract-abi-data