sigit/sigit.io
7
2
Fork 0
Code Issues 32 Pull Requests 2 Actions Packages Projects 1 Releases 5 Wiki Activity

Show block # on user profile #1

New Issue
Closed
opened 2024-05-02 10:40:39 +00:00 by b · 1 comment
b commented 2024-05-02 10:40:39 +00:00
Owner
Copy Link

Show block # for all profiles, eg:

image

This can be achieved by scanning all relays for the oldest note. The feature can be gamed, eg by signing a very old note, and can be unreliable, eg if the old notes are deleted. Still, it's the best we can do until timestamp attestations become the norm.

To convert a timestamp to a block number, see this thread (correct explorer link is in a comment under the answer): https://stackoverflow.com/questions/53788151/getting-bitcoins-block-number-in-a-specific-date-and-hour

The text itself can be a link to the note, eg below

https://njump.me/nevent1qqsraslp7mt6659yjc294xmh8uualujxd763hysqv8uye50k2jk5wggppemhxue69uhkummn9ekx7mp0qgsxu35yyt0mwjjh8pcz4zprhxegz69t4wr9t74vk6zne58wzh0waycrqsqqqqqpj2yrdr

Show block # for all profiles, eg: ![image](/attachments/54544584-158c-4338-b232-7df55fa735bb) This can be achieved by scanning all relays for the oldest note. The feature can be gamed, eg by signing a very old note, and can be unreliable, eg if the old notes are deleted. Still, it's the best we can do until timestamp attestations become the norm. To convert a timestamp to a block number, see this thread (correct explorer link is in a comment under the answer): https://stackoverflow.com/questions/53788151/getting-bitcoins-block-number-in-a-specific-date-and-hour The text itself can be a link to the note, eg below https://njump.me/nevent1qqsraslp7mt6659yjc294xmh8uualujxd763hysqv8uye50k2jk5wggppemhxue69uhkummn9ekx7mp0qgsxu35yyt0mwjjh8pcz4zprhxegz69t4wr9t74vk6zne58wzh0waycrqsqqqqqpj2yrdr
image.png
60 KiB
b changed title from Show block # for new users to Show block # on user profile 2024-05-02 10:46:10 +00:00
s self-assigned this 2024-05-07 07:44:28 +00:00
s commented 2024-05-10 11:11:43 +00:00
Owner
Copy Link

closed by PR #18

closed by PR #18
s closed this issue 2024-05-10 11:11:43 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Kind/Breaking
Breaking change that won't be backward compatible
Kind/Bug
Something is not working
Kind/Documentation
Documentation changes
Kind/Enhancement
Improve existing functionality
Kind/Feature
New functionality
Kind/Security
This is security issue
Kind/Testing
Issue or pull request related to testing
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
Reviewed
Confirmed
Issue has been confirmed
Reviewed
Duplicate
This issue or pull request already exists
Reviewed
Invalid
Invalid issue
Reviewed
Won't Fix
This issue won't be fixed
Status
Abandoned
Somebody has started to work on this but abandoned work
Status
Blocked
Something is blocking this issue or pull request
Status
Need More Info
Feedback is required to reproduce issue or to continue work
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees s
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sigit/sigit.io#1
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?