orenyodfat

also `repRewardConstA and repRewardConstB`

please add also `batchesIndexCap` https://github.com/daostack/arc/blob/master/contracts/schemes/ContinuousLocking4Reputation.sol#L54 @ben-kaufman

what is the reason for the client/alchemy to have these contracts abis ?

though reputation and daotokens contracts are owned by the controller. any write operations (state change) can not be done directly with these contracts

sound like a good direction. can we use the "gateway" / Apollo Federation without support/update of the graph-node ? any experience using the "gateway" ?

Is there a need to index it ? On Tue, 29 Oct 2019 at 16:35 Jordan Ellis wrote: > The DAORegistryContract entity > > is never added to the store...

@jellegerbrandy why you are quiering for specific version ? You should query with the contract address ..

arc.js should wait to tx via web3 and not via truffle .

👍🏽 On Sat, 28 Jul 2018 at 15:25 Doug Kent wrote: > @tibetsprague This could perhaps be > used to handle in a single fetcher the GP and CR events...

fetch events by block can be done by web3 . are you referring to a more sophisticate wrapper which could aggregate multiple event sources to one output?