Interface Between the BlockCerts App and the Issuer URL


#1

We are trying to build a demo of the entire process of blockchain based certification using the Blockcerts app.

We have been able to issue certificates and successfully get it verified using the cert-issuer and web based verifier .

Now, we are trying to interface the Blockcerts app with our server, so that the User can add us as a Issuer and get our issued certificates on their Blockcerts app. We are unsure how to do this in terms of setting up our server to communicate with the app.

By reading from the discussions here, it seems that the app will call the Issuer URL that the user provides, with the public address of the user. We are unsure how to receive this call on our server and what should be the feedback (content and format) that the server needs to send back to the app.

Can someone help us out with this and/or point us to some documentation/discussion that makes this point clear?


#2

I found this post: Learning Machine Contributes Android App to Blockcerts it looks like we need to respond with JSON like what’s at https://github.com/blockchain-certificates/BlockcertsFramework-iOS/blob/master/Frameworks/BlockcertsTests/Resources/Issuers/issuer-v2.json but with our issuer details obviously.


#3

Cool. Thanks @stuartf.

Do you know how to receive this HTTP call on the issuer side? so as to grab the Public Address of the user that is supposed to be present on the http call payload?


#4

I think that first request is just a GET without any parameters. Then I think it will POST with the user’s public key and an optional one time shared token to the introductionUrl from the issuer details.


#5

Thanks!

Was able to track the POST request from the app.

Looks like this.

print request.data
{“bitcoinAddress”:“xxxxxxxxxxxx”,“nonce”:“yyyyyy”}

Its public address for a bitcoin wallet.
I was looking to get the whole demo working on Ethereum chain…


#6

Address from the mobile app is primarily for signing keys.

It could be any sort of priv/pub key and it would work just the same. With our current implementation, there’s no need to have this be chain specific, especially since transactions are not sent to the recipients anyways, only referenced inside the blockcert.

FYI, since you’re going down that pathway right now, I have to mention that Ethereum verification inside the mobile app is currently in the works. So you’ll be able to import the certificate but not verify yet.


#7

Thanks @aronning

Okays. Yes, knew that the transactions are sent to a burn address.
So, This pub key would be unique to the particular user. That would be enough as an identity for the user.
Cool, We will use this public address for issuing the blockcert.

And, thanks for the verification on the mobile app info. This was going to be my upcoming post on the forum :slight_smile: , as I saw yesterday that verification was not initiating on the app.


#8

Yup, each blockcerts app is essentially a wallet with that regards. Right now they don’t do a whole lot, but we’ve talked about some cool functionality that would rely on those addresses/signatures :slight_smile:


#9

More cooler functionality with the app… Looking forward to that!!