robrobbins
robrobbins
closed as I will open a new PR once #1414 is merged to `main`.
haven't forgotten this. just busy... i'll get there got some time today and sketched out what a type2 decode may look like, assuming it returns a tx struct. i'll flush...
admit it, you laughed at this like me... > Rollups are in the short and medium term, and possibly in the long term...
sweet! Let me go land this little feature and then i'll get a PR started.
OK. With a minor adjustment to the handling of the `v_int` (when its 28) this looks to work. GREAT. LFG!.. I made some comments over on the livebook for things...
I'll likely post issue as a follow up, which i can do later for decoding the input data. I'm handling `transfer` events exclusively so it's a simple matter to strip...
getting started on #100 . got to go put out other fires rest of the day, but i'll keep hacking as i get time.
gunna get some time back in here today. @alisinabh i think to be useful i'll need both the present legacy -- and more importantly the same for type2. playing around...
SMH. While i kind of suspect the access_list, I'm still scratching my head here on why a decoded type2 signed tx won't recover the correct address: raw: 0x02f8a70103020482a41094826180541412d574cf1336d22c0c0a287822678a80b844a9059cbb000000000000000000000000b1228c21546e3848498169f4241ab63279d502d5000000000000000000000000000000000000000000000000000000e8d4a51000c080a0b37b7057eaf42412f834b4e3f1cd00ed4a346381a c2bdd7ddc2fad48619453b3a00868d3423b2e365793bc691be1f7611e3d09c8e883535a1d7f25c2d2f8ee514c ^...