hush
/
hush3
9
0
Fork 11
Code Issues 143 Pull Requests 3 Projects Releases 16 Wiki Activity
Labels Milestones
New Issue

getrawtransaction RPC docs result example only includes transparent #114

Open
opened 2 years ago by duke · 3 comments
duke commented 2 years ago
Owner

https://faq.hush.is/rpc/getrawtransaction.html

Our RPC docs do not show what it looks like when a zaddr is involved in a tx

https://faq.hush.is/rpc/getrawtransaction.html Our RPC docs do not show what it looks like when a zaddr is involved in a tx
duke changed title from getrawtransaction result example only includes transparent to getrawtransaction RPC docs result example only includes transparent 2 years ago
jahway603 commented 2 years ago
Collaborator

Is this issue related to this other issue #118?

Is this issue related to this other issue https://git.hush.is/hush/hush3/issues/118?
duke commented 2 years ago
Poster
Owner

@jahway603 it's different. This issue is to show some example output from a transaction that has zaddrs involved, to show the structure of the JSON. Currently the docs only show the JSON output for transactions involving only taddrs

@jahway603 it's different. This issue is to show some example output from a transaction that has zaddrs involved, to show the structure of the JSON. Currently the docs only show the JSON output for transactions involving only taddrs
duke commented 2 years ago
Poster
Owner

@jahway603 also a word of warning, you don't want to show real data from a ztx you own in the docs, that is not public data. We want to show what JSON keys are returned, and what the data looks like, but we should jumble the actual data so as to not leak real metadata. Another way to do it would be to make a new HSC for testing, make a ztx on that, and then you can put the exact data without worrying about metadata leakage. The first way is probably less work.

@jahway603 also a word of warning, you don't want to show real data from a ztx you own in the docs, that is not public data. We want to show what JSON keys are returned, and what the data looks like, but we should jumble the actual data so as to not leak real metadata. Another way to do it would be to make a new HSC for testing, make a ztx on that, and then you can put the exact data without worrying about metadata leakage. The first way is probably less work.
duke added the
documentation
 label 1 year ago
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
arm
asyncnotedecryption
danger
dev
dev-aarch64
dev-mac
dev-old-randomx
divzaddrs
dragonx
duke
freebsd
getfilterednotes
hip39
hushutils
insync
jahway603
master
mvstuff
onryo
p2p_privacy
ramhash
relaytx
rx-largepages
setbestchain
warmup
witness_cache
wolfssl
wolfssl_win
z_createrawtransaction
z_importwallet
z_signmessage
Labels
Apply labels
Clear labels
0-500 bounty
bounty up to 500 HUSH 2001-5000 bounty
bounty between 2001 and 5000 HUSH 501-2000 bounty
bounty between 501 and 2000 HUSH arm
something doesn't work on arm beginners
for new developers bug
may or may not be a bug build
problems building documentation
not enough information feature
new feature high priority
high priority i2p
related to i2p low priority
low priority medium priority
medium priority question
something is not clear release
release label or issue related to it testing
related to testing tor
related to tor wontfix
this won't be fixed
No Label 0-500 bounty 2001-5000 bounty 501-2000 bounty arm beginners bug build documentation feature high priority i2p low priority medium priority question release testing tor wontfix
Milestone
Set milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Assign users
Clear assignees
No Assignees
2 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Write Preview
Loading…
Cancel
Save
There is no content yet.
Delete Branch '%!s(MISSING)'

Deleting a branch is permanent. It CANNOT be undone. Continue?

No
Yes