Blog Post: Call for Applications: Privacy at Bitcoin's Base Layer (Spring 2026)#672
Open
Blog Post: Call for Applications: Privacy at Bitcoin's Base Layer (Spring 2026)#672
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
btcschellingpt
approved these changes
Apr 28, 2026
dergigi
reviewed
Apr 29, 2026
Member
dergigi
left a comment
dergigi
left a comment
There was a problem hiding this comment.
Yes, let's ship it! 
Last thing to do is bump the date & update the authors.
dergigi
reviewed
Apr 29, 2026
Member
|
Damn, I just remembered that I promised to update the button style 😭 |
Mirrors the v2 donate banner pattern from PR #673 so an apply-for-a-grant button can share the same orange-gradient banner aesthetic with hover animation, dark-mode support, and a mobile-optimized layout.
Provides a stylish call-to-apply banner that shares the v2 banner aesthetic with the donate button. Defaults route to /apply, with an optional `track` for the LTS program or a custom `href` override, and prelude/cta/tagline slots so blog posts can tailor the copy.
Replace the two hand-rolled "Apply for a Grant" buttons in the spring 2026 call-for-applications post with the new ApplyButton, giving the post the v2 banner aesthetic with mobile, dark-mode, and reduced-motion support. The first banner introduces the funding focus, and the second nudges readers toward submitting after they've read the pitch.
The cta uses a shell-prompt motif ('>_ apply'), so a trailing question
mark broke the command-line aesthetic. The prelude 'Ready to' flows fine
into 'apply' without it.
Member
|
Button style updated, will merge as soon as someone from @OpenSats/content had another look 👀 |
'Ready to >_ apply?' reads as the intended call-and-response, so the question mark stays.
The default landing for an "apply for a grant" CTA should be the grant application form itself, not the broader /apply landing page.
Arvin21M
commented
Apr 29, 2026
Contributor
Author
There was a problem hiding this comment.
New buttons look good on build preview on desktop.
I like how the second one asks a question to offer up variety.
Button on mobile view looks a bit tall, perhaps match pixel height on mobile to how it is on desktop if any different?
Also, when in mobile view, the wording changes to "apply" on the left, and "apply for a grant" on the right, on both buttons.
The desktop view is fine with varying messages between the two buttons, and between he message on the right and left of the button.
Contributor
|
Generally, LGTM! |
Drops min-height from 120px to 88px under 480px, tightens vertical padding, and trims the cta font slightly so the banner sits more comfortably in the reading flow on phones.
Both BIPs have dedicated /topics pages on the OpenSats site, so the references in the privacy spring 2026 post should point readers there instead of off-site to the BIP repository.
Payjoin (covers PDK and Async Payjoin), Floresta, and BDK each have dedicated project pages on the OpenSats site, so prefer those over the grant-announcement blog anchors. Silent Payments, Coinswap, JoinMarket NG, ASmap, rust-bitcoin, and Kyoto don't have project pages yet, so their references stay on the grant posts.
Repoint the inline Payjoin link from /topics/payjoin to /projects/payjoin to match the other Payjoin references in this post.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Build Preview:
Header Image Preview: