Cloud, Blockchain, Crypto & Web3 Technology Enthusiast, Evangelist & Educator
Cloud, Blockchain, Crypto & Web3 Technology Enthusiast, Evangelist & Educator

Subscribe to Coffee & Crypto

Subscribe to Coffee & Crypto
Share Dialog
Share Dialog


<100 subscribers
<100 subscribers
When we last left off, I was omega frustrated, not only because I lost the entire draft of my blog post but also because I was unable to use the Arweave GraphQL Explorer to return a list of all of my posts.
I had the idea of just making sure that my posts were showing up as transactions on the Arweave block explorer. However, when I put my wallet address into the block explorer, there were no results. I am sure there is a perfectly valid reason for this, I just don’t know what it is. Then I noticed that like all block explorers, you can also put in a transaction ID. I did have one of these from my previous blog post where I used the post digest to return a transaction ID. When I put the transaction ID into the block explorer, this is what I got. You will notice the box highlighted in red is my wallet address.

Ok, so I knew about this before and was unable to get it to work and couldn’t figure out why. I am able to get it to work now using the code sample below.
query GetMirrorTransactions($contributor: String!) {
transactions(tags:[
{
name:"App-Name",
values:["MirrorXYZ"],
},
{
name:"Contributor",
values:[$contributor]
}
], sort:HEIGHT_DESC, first: 10){
edges {
node {
id
}
}
}
}
What was different this time than last time? Where it says name:”Contributor”, I was using name:”contributor”. Apparently the capitalization matters a lot. My background is in things like PowerShell where it doesn’t matter if you capitalize things or not.
Lesson Learned.
When we last left off, I was omega frustrated, not only because I lost the entire draft of my blog post but also because I was unable to use the Arweave GraphQL Explorer to return a list of all of my posts.
I had the idea of just making sure that my posts were showing up as transactions on the Arweave block explorer. However, when I put my wallet address into the block explorer, there were no results. I am sure there is a perfectly valid reason for this, I just don’t know what it is. Then I noticed that like all block explorers, you can also put in a transaction ID. I did have one of these from my previous blog post where I used the post digest to return a transaction ID. When I put the transaction ID into the block explorer, this is what I got. You will notice the box highlighted in red is my wallet address.

Ok, so I knew about this before and was unable to get it to work and couldn’t figure out why. I am able to get it to work now using the code sample below.
query GetMirrorTransactions($contributor: String!) {
transactions(tags:[
{
name:"App-Name",
values:["MirrorXYZ"],
},
{
name:"Contributor",
values:[$contributor]
}
], sort:HEIGHT_DESC, first: 10){
edges {
node {
id
}
}
}
}
What was different this time than last time? Where it says name:”Contributor”, I was using name:”contributor”. Apparently the capitalization matters a lot. My background is in things like PowerShell where it doesn’t matter if you capitalize things or not.
Lesson Learned.
No activity yet