Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix rollup resolution #532

Merged
merged 3 commits into from
Sep 4, 2024
Merged

Fix rollup resolution #532

merged 3 commits into from
Sep 4, 2024

Conversation

PJColombo
Copy link
Member

@PJColombo PJColombo commented Sep 4, 2024

Checklist

  • My change requires a documentation update, and I have done it.
  • I have added tests to cover my changes.
  • I have filled out the description and linked the related issues.

Description

It corrects the indexing procedure to resolve the rollup address from the transactions' sender rather than the receiver.

Motivation and Context (Optional)

Related Issue (Optional)

Screenshots (if appropriate):

Copy link

vercel bot commented Sep 4, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
blobscan-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Sep 4, 2024 1:25am
blobscan-staging ✅ Ready (Inspect) Visit Preview 💬 Add feedback Sep 4, 2024 1:25am
4 Skipped Deployments
Name Status Preview Comments Updated (UTC)
blobscan-gnosis ⬜️ Ignored (Inspect) Visit Preview Sep 4, 2024 1:25am
blobscan-holesky ⬜️ Ignored (Inspect) Visit Preview Sep 4, 2024 1:25am
blobscan-mainnet ⬜️ Ignored (Inspect) Sep 4, 2024 1:25am
blobscan-sepolia ⬜️ Ignored (Inspect) Visit Preview Sep 4, 2024 1:25am

Copy link

changeset-bot bot commented Sep 4, 2024

🦋 Changeset detected

Latest commit: 1b0d03e

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@blobscan/api Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

Copy link
Contributor

github-actions bot commented Sep 4, 2024

📦 Next.js Bundle Analysis for @blobscan/web

This analysis was generated by the Next.js Bundle Analysis action. 🤖

⚠️ Global Bundle Size Increased

Page Size (compressed)
global 275.25 KB (🟡 +29.63 KB)
Details

The global bundle is the javascript bundle that loads alongside every page. It is in its own category because its impact is much higher - an increase to its size means that every page on your website loads slower, and a decrease means every page loads faster.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

If you want further insight into what is behind the changes, give @next/bundle-analyzer a try!

Eleven Pages Changed Size

The following pages changed size from the code in this PR compared to its base branch:

Page Size (compressed) First Load % of Budget (350 KB)
/ 352.3 KB 627.56 KB 179.30% (🟢 -4.87%)
/address/[address] 27.31 KB 302.56 KB 86.45% (🟢 -4.70%)
/blob/[hash] 26.32 KB 301.58 KB 86.17% (🟢 -4.61%)
/blobs 75.54 KB 350.79 KB 100.23% (🟡 +12.20%)
/block/[id] 12.64 KB 287.89 KB 82.26% (🟢 -4.64%)
/blocks 73.26 KB 348.51 KB 99.58% (🟡 +12.19%)
/stats/blob 336.48 KB 611.74 KB 174.78% (🟢 -4.80%)
/stats/block 337.51 KB 612.77 KB 175.08% (🟢 -4.80%)
/stats/tx 336.61 KB 611.86 KB 174.82% (🟢 -4.80%)
/tx/[hash] 14.07 KB 289.33 KB 82.67% (🟡 +0.23%)
/txs 72.73 KB 347.99 KB 99.42% (🟡 +10.19%)
Details

Only the gzipped size is provided here based on an expert tip.

First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

The "Budget %" column shows what percentage of your performance budget the First Load total takes up. For example, if your budget was 100kb, and a given page's first load size was 10kb, it would be 10% of your budget. You can also see how much this has increased or decreased compared to the base branch of your PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this. If you see "+/- <0.01%" it means that there was a change in bundle size, but it is a trivial enough amount that it can be ignored.

Copy link

codecov bot commented Sep 4, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.88%. Comparing base (a58cb55) to head (1b0d03e).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #532   +/-   ##
=======================================
  Coverage   89.88%   89.88%           
=======================================
  Files         148      148           
  Lines        9699     9699           
  Branches     1026     1026           
=======================================
  Hits         8718     8718           
  Misses        981      981           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@PJColombo PJColombo merged commit 03fb6b0 into main Sep 4, 2024
14 checks passed
@PJColombo PJColombo deleted the fix-rollup-resolution branch September 4, 2024 01:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant