1: Seriously, why is no one talking about AccessControlledAggregator contracts (ACA)
Bear with me on this one
25 Jun #Chainlink creates 30 ACA’s (ACA#1)
6 Aug #Chainlink creates 39 more ACA’s (ACA#2)
Remember these are in addition to the regular Aggregator contracts
Cont…
Bear with me on this one
25 Jun #Chainlink creates 30 ACA’s (ACA#1)
6 Aug #Chainlink creates 39 more ACA’s (ACA#2)
Remember these are in addition to the regular Aggregator contracts
Cont…
2: Let that sink in, we have a bunch of regular Aggregator contracts working away and now we also have 2 almost identical sets of ACA contracts running jobs.
Now, why would #Chainlink do this I wonder?
BTW market.link calls ACA contracts fluxaggregators
Cont….
Now, why would #Chainlink do this I wonder?
BTW market.link calls ACA contracts fluxaggregators
Cont….
3: So here comes the interesting part
@linkpoolio latest distribution was 4167 (for 3 weeks)
Payment breakdown
Aggregators: 2237
ACA #1 contracts: 1647
ACA #2 contracts: 273.58
Don’t trust me on this, check it out
Cont…
@linkpoolio latest distribution was 4167 (for 3 weeks)
Payment breakdown
Aggregators: 2237
ACA #1 contracts: 1647
ACA #2 contracts: 273.58
Don’t trust me on this, check it out
Cont…
4: So the question arises why does #Chainlink have what are essentially identical sets of contracts resulting in multiple payouts to node operators like @linkpoolio? Unless these contracts are bespoke solutions for certain entities!
Now who and what might use something like this?
Now who and what might use something like this?
• • •
Missing some Tweet in this thread? You can try to
force a refresh
