Avatar
Glacier
23fffd0a223631a325e38d4e31a164b052536f0a14cd5be2ab29f3bcc837f979

Perhaps there's some way for a version of a mining pool nostr:npub1qtvl2em0llpnnllffhat8zltugwwz97x79gfmxfz4qk52n6zpk3qq87dze s proposed solution for miners to construct their own block templates, for a nostr version to support solo/larger/all relays to construct their own content templates?

It's a delicate balance, guess this is the behind the scenes world of any content platform, confident that the #nostrmind can solve this.

Bitcoin is only starting out on the mission of decentralising mining nostr:npub1ql2zzp3g6yndgz05js7wdc4qkr88wkyne5nw2cc7csrtzqs0yeesgwrxya nostr:npub1k8s3skyy5mg5h07w8zvuk5lgrqadmejz7fjdpl60zaznw8sxzdxqxm6y88 feels like we should get the jump on the relays before we end up with the big 3...

nostr:npub1te0uzs6vj29umjaxlqqct82j8q6ppyefrxq06dhr8d6pvwfatgkqjmjgwp

nostr:npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk

@Bitcoin Mechanic

npub1wnlu28xrq9gv77dkevck6ws4euej4v568rlvn66gf2c428tdrptqq3n3wr

Guess they invested the time and got frequently rewarded with success. Perhaps the stickiness of a product is enhanced by a learning curve which is a little steeper than it needs to be?

Hashing the Hash #·#

Simplifying visual verification of hashes

The convenience of QR codes for transactions is undeniable. However, they come with a significant drawback: they are not human-readable. This poses a challenge for users who need to verify addresses and transaction IDs. Typically, we find ourselves squinting at the screen, checking the first and last few characters of a hash, a process that is both tedious and prone to errors.

To address this issue, perhaps a novel solution: 'hashing the hash' #·# Using algorithms like CRC 16 or Pearson hashing to generate a short hash transforming a lengthy, complex hash into a dynamic symbol that is quickly and easily readable. Someone more qualified nostr:npub1qg8j6gdwpxlntlxlkew7eu283wzx7hmj32esch42hntdpqdgrslqv024kw nostr:npub1az9xj85cmxv8e9j9y80lvqp97crsqdu2fpu3srwthd99qfu9qsgstam8y8 would have to confirm how much complexity is ’enough’. Potentially include timestamp in the generation of the short hash to prevent someone from creating an alternative hash that results in the same short hash (within a relatively short timeframe). This approach could simplify the verification process.

The design of the visual aspect / dynamic symbol is crucial. It must be simple enough for quick recognition while remaining ‘complex enough’. The symbol could be a combination of shapes, colors (although B&W probably more universal) or patterns that represent the hashed value of the transaction ID or bitcoin/lightning address. https://satsymbol.com nostr:npub1xkr96pkrasvvrfuclyx6esudrfhyxgk064amcf38dcq6p0aa0wustww52l (a simple watch face provides 12 x 60 x 60)

It could serve as a safeguard against threats like clipboard hijacking or malicious QR code replacements, providing users with a reliable visual reference for transaction verification. From a user experience standpoint, hashing the hash could enhance the way we handle small transactions. With a quick visual reference, users could comfortably verify transactions without the need for meticulous hash checks, saving time and reducing anxiety.

Next time you find yourself squinting at the last characters of a TXID... it could be good

See below example:

Keen if anyone else is interested in this? nostr:npub1a2cww4kn9wqte4ry70vyfwqyqvpswksna27rtxd8vty6c74era8sdcw83a (ever think about those onna-musha Mizu bitcoin glasses?) nostr:npub1ahxjq4v0zlvexf7cg8j9stumqp3nrtzqzzqxa7szpmcdgqrcumdq0h5ech

Or if there are other projects exploring this? nostr:npub1getal6ykt05fsz5nqu4uld09nfj3y3qxmv8crys4aeut53unfvlqr80nfm nostr:npub1mutnyacc9uc4t5mmxvpprwsauj5p2qxq95v4a9j0jxl8wnkfvuyque23vg nostr:npub1ex7mdykw786qxvmtuls208uyxmn0hse95rfwsarvfde5yg6wy7jq6qvyt9

First note on nostr - hopefully doing it right

{0,o}

nostr:npub1cyla8qgt9gv8y6ydv8s2prt89h8afc0sr2kaz64ryjmlpdrzxm4qwlh53q interested is the POS setup at Fox hotel where should I find more info?