psf/psf-memo
1
0
Fork 0
mirror of https://github.com/Permissionless-Software-Foundation/psf-memo.git synced 2026-09-21 16:52:01 -07:00
Code Issues Packages Projects Releases Wiki Activity

Specify binary hash160 broadcast payload for follow/mute

Browse Source 
Client follow/mute (and their inverse unmute/unfollow) must broadcast the
target's raw 20-byte hash160 as the OP_RETURN payload and must not depend on
the Node-only Buffer global. Adds the Binary Payload Broadcast regression
spec covering the binary payload for all four actions.

By specifier.
This commit is contained in:
Chris Troutner
2026-09-04 11:07:25 -07:00
parent 5602975a37
commit 62e04799c8
1 changed files with 54 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
psf-memo-client/specs/binary-payload-broadcast.feature
+54
View File
@@ -0,0 +1,54 @@
# Scenarios: Binary Payload Broadcast - 1, Binary Payload Broadcast - 2, Binary Payload Broadcast - 3, Binary Payload Broadcast - 4
#
# Follow/unfollow and mute/unmute broadcast an OP_RETURN whose payload is the
# target's raw 20-byte hash160, not its display-form cash address text. This
# regression spec exercises that binary payload on the wire for every action.
# The coder must keep the payload bytes exact and must not surface a broadcast
# error after a successful action.
Feature: Binary Payload Broadcast
Background:
Given a wallet authenticated for the address bitcoincash:qqlrzp23w08434twmvr4fxw672whkjy0py26r63g3d
Given the wallet has spendable output to pay the transaction fee
Scenario Outline: Binary Payload Broadcast - 1 clicking Mute broadcasts the binary hash160 payload for the address <addr>
Given I open the profile page for the address <addr>
When I click the Mute button
Then the app broadcasts an OP_RETURN transaction with the Memo mute prefix and the binary hash160 payload for the address <addr>
Then the profile page shows an Unmute button
Examples:
| addr |
| bitcoincash:qr95sy3j9xwd2ap32xkykttr4cvcu7as4y0qverfuy |
Scenario Outline: Binary Payload Broadcast - 2 clicking Unmute broadcasts the binary hash160 payload for the address <addr>
Given the psf-memo-db API reports that I mute the address <addr>
Given I open the profile page for the address <addr>
When I click the Unmute button
Then the app broadcasts an OP_RETURN transaction with the Memo unmute prefix and the binary hash160 payload for the address <addr>
Then the profile page shows a Mute button
Examples:
| addr |
| bitcoincash:qr95sy3j9xwd2ap32xkykttr4cvcu7as4y0qverfuy |
Scenario Outline: Binary Payload Broadcast - 3 clicking Follow broadcasts the binary hash160 payload for the address <addr>
Given I open the profile page for the address <addr>
When I click the Follow button
Then the app broadcasts an OP_RETURN transaction with the Memo follow prefix and the binary hash160 payload for the address <addr>
Then the profile page shows an Unfollow button
Examples:
| addr |
| bitcoincash:qr95sy3j9xwd2ap32xkykttr4cvcu7as4y0qverfuy |
Scenario Outline: Binary Payload Broadcast - 4 clicking Unfollow broadcasts the binary hash160 payload for the address <addr>
Given the psf-memo-db API reports that I follow the address <addr>
Given I open the profile page for the address <addr>
When I click the Unfollow button
Then the app broadcasts an OP_RETURN transaction with the Memo unfollow prefix and the binary hash160 payload for the address <addr>
Then the profile page shows a Follow button
Examples:
| addr |
| bitcoincash:qr95sy3j9xwd2ap32xkykttr4cvcu7as4y0qverfuy |