Pages:
Author

Topic: Holy Grail BOUNTY - page 11. (Read 36328 times)

sr. member
Activity: 440
Merit: 251
June 06, 2013, 11:18:42 PM
#44
I know that OT uses 'mailboxes' for unsigned transactions and even invoices / messages etc.  Is the idea to replace the mailbox infrastructure with BitMessage?

Absolutely not. OT's inboxes (and other boxes) are integral to the internal workings of OT. (And everything in them is signed.)

Bitmessage is an additional layer to be used for discovery, specifically for server-to-server wiring and cross-server exchange. It will be used with OT, inside this GUI (this thread), which will integrate with both of them.

Quote
Or would all messages be directed to a specific OT server identified by a BM address and thus simply replace the HTTP protocol for communicating with an OT server?

Absolutely not. Bitmessage will not change anything inside OT itself. Rather, this "holy grail" application will use both OT and Bitmessage.

Also, FYI, the Bitmessage communications will not be between OT servers, but P2P between OT users.
hero member
Activity: 770
Merit: 566
fractally
June 06, 2013, 07:48:51 PM
#43
Lets just say I have dual use for BitMessage integration and I will leave the GUI to you.  The annoying thing about bitmessage is that it depends upon PyQt is and is a pain to deploy.   It would be nice if there were a Qt GUI for bitmessage that integrated at the protocol level... but I suspect that would require a bigger bounty and is outside the scope of this.

I don't suppose the creator can open up a HTTP/JSON API so we can interface into it with out creating a QT/C++ version of bitmessage? I'm not sure which one would be easier/secure
It does have a json-api, but you still need to deploy the app.  I suppose if you used it without the GUI it might be easier to deploy.
legendary
Activity: 3920
Merit: 2349
Eadem mutata resurgo
June 06, 2013, 07:26:26 PM
#42
I know that OT uses 'mailboxes' for unsigned transactions and even invoices / messages etc.  Is the idea to replace the mailbox infrastructure with BitMessage?
Or would all messages be directed to a specific OT server identified by a BM address and thus simply replace the HTTP protocol for communicating with an OT server?

Probably read the OP of the original idea will bring you up to speed. BM is just for P2P price discovery, not settlement, escrow or clearing functions.

https://bitcointalksearch.org/topic/m.2227866
legendary
Activity: 980
Merit: 1003
I'm not just any shaman, I'm a Sha256man
June 06, 2013, 03:10:25 PM
#41
Lets just say I have dual use for BitMessage integration and I will leave the GUI to you.  The annoying thing about bitmessage is that it depends upon PyQt is and is a pain to deploy.   It would be nice if there were a Qt GUI for bitmessage that integrated at the protocol level... but I suspect that would require a bigger bounty and is outside the scope of this.

I don't suppose the creator can open up a HTTP/JSON API so we can interface into it with out creating a QT/C++ version of bitmessage? I'm not sure which one would be easier/secure
hero member
Activity: 770
Merit: 566
fractally
June 06, 2013, 01:04:41 PM
#40
I know that OT uses 'mailboxes' for unsigned transactions and even invoices / messages etc.  Is the idea to replace the mailbox infrastructure with BitMessage?

Or would all messages be directed to a specific OT server identified by a BM address and thus simply replace the HTTP protocol for communicating with an OT server?

hero member
Activity: 770
Merit: 566
fractally
June 06, 2013, 01:02:02 PM
#39
I am interested in BitMessage integration.

And if there is a 'market' GUI potentially that too.

All i know is that I claimed the systray gui part, and the HTTP interface so that it can accept commands. I hear you bitmessage is still open and I've heard that you know how to get it integrated, you should message me and we will work together, if you claim the bitmessage part Smiley


I understand that OT is open source like Ripple,

Currently Ripple is *not* open source (and it needs XRP which OT does not).

Ah, I see they have a GitHub, but no source files. Suspicious Scam.

Me an felllowtravler were discussing diff qt versions last night, today I will post what i have so far to the githubpage, or you can check out my github page to see that i forked the project already and posted up some things https://github.com/Xenland/Moneychanger

Lets just say I have dual use for BitMessage integration and I will leave the GUI to you.  The annoying thing about bitmessage is that it depends upon PyQt is and is a pain to deploy.   It would be nice if there were a Qt GUI for bitmessage that integrated at the protocol level... but I suspect that would require a bigger bounty and is outside the scope of this.
legendary
Activity: 980
Merit: 1003
I'm not just any shaman, I'm a Sha256man
June 06, 2013, 12:51:48 PM
#38
I am interested in BitMessage integration.

And if there is a 'market' GUI potentially that too.

All i know is that I claimed the systray gui part, and the HTTP interface so that it can accept commands. I hear you bitmessage is still open and I've heard that you know how to get it integrated, you should message me and we will work together, if you claim the bitmessage part Smiley


I understand that OT is open source like Ripple,

Currently Ripple is *not* open source (and it needs XRP which OT does not).

Ah, I see they have a GitHub, but no source files. Suspicious Scam.

Me an felllowtravler were discussing diff qt versions last night, today I will post what i have so far to the githubpage, or you can check out my github page to see that i forked the project already and posted up some things https://github.com/Xenland/Moneychanger
donator
Activity: 1736
Merit: 1014
Let's talk governance, lipstick, and pigs.
June 06, 2013, 10:43:49 AM
#37
I am a little surprised that Namecoin isn't in the mix here.
donator
Activity: 1736
Merit: 1014
Let's talk governance, lipstick, and pigs.
June 06, 2013, 10:19:55 AM
#36
I understand that OT is open source like Ripple,

Currently Ripple is *not* open source (and it needs XRP which OT does not).

Ah, I see they have a GitHub, but no source files. Suspicious Scam.
legendary
Activity: 1890
Merit: 1086
Ian Knowles - CIYAM Lead Developer
June 06, 2013, 10:07:25 AM
#35
I understand that OT is open source like Ripple,

Currently Ripple is *not* open source (and it needs XRP which OT does not).
donator
Activity: 1736
Merit: 1014
Let's talk governance, lipstick, and pigs.
June 06, 2013, 10:05:04 AM
#34
I understand that OT is open source like Ripple, but is it also centralized like Ripple as well? What makes OT any different than Ripple? Bitmessage is a decentralized messaging system that could relay Ripple gateways as well as OT servers could it not?
hero member
Activity: 770
Merit: 566
fractally
June 06, 2013, 08:38:43 AM
#33
I am interested in BitMessage integration.

And if there is a 'market' GUI potentially that too.
sr. member
Activity: 440
Merit: 251
June 06, 2013, 02:08:15 AM
#32
--- In the protocol, I am assuming it's the same asset type on both servers (same issuer.) You would need the same asset type ID in order for the discovery to work over Bitmessage the way I've described.
If it is the same asset type ID I'm not sure why would Alice want to transfer it from Server A to Server B for a fee. Who is the beneficiary of that transfer on Server B?

Alice.
legendary
Activity: 3431
Merit: 1233
June 06, 2013, 01:57:25 AM
#31
--- In the protocol, I am assuming it's the same asset type on both servers (same issuer.) You would need the same asset type ID in order for the discovery to work over Bitmessage the way I've described.
If it is the same asset type ID I'm not sure why would Alice want to transfer it from Server A to Server B for a fee. Who is the beneficiary of that transfer on Server B?
sr. member
Activity: 440
Merit: 251
June 06, 2013, 01:25:13 AM
#30
Quote
Let's say Alice is someone who wants to transfer Silver Grams from Server A to Server B.
Are Silver Grams from Server A and Silver Grams from Server B issued by different Issuers? If so then they'll be totally different assets.

--- In the protocol, I am assuming it's the same asset type on both servers (same issuer.) You would need the same asset type ID in order for the discovery to work over Bitmessage the way I've described.

--- But I guess you could do it either way. A slightly modified version of the protocol would be used in the case where they are different issuers.

--- I'd think if we're talking about two different asset types, then Alice would simply convert the asset type first (on the market) and then perform the wire. (Of course a smart wallet could automate this for her.)

Quote
If Bob is willing to exchange Asset B against Asset A then he has to maintain Asset B account on Server A? Is that correct?

--- This is correct.

--- The servers could also maintain accounts with each other.

--- You could also convert the asset to BTC on the market, and then move it to any server, and then convert it back.
legendary
Activity: 3431
Merit: 1233
June 06, 2013, 01:10:36 AM
#29


Quote
Let's say Alice is someone who wants to transfer Silver Grams from Server A to Server B.
Are Silver Grams from Server A and Silver Grams from Server B issued by different Issuers? If so then they'll be totally different assets. If Bob is willing to exchange Asset B against Asset A then he has to maintain Asset B account on Server A? Is that correct?
legendary
Activity: 980
Merit: 1003
I'm not just any shaman, I'm a Sha256man
June 06, 2013, 12:37:52 AM
#28
Tasks.  (Since several people have volunteered, I'd like you to specify tasks you are going to own.)

--- Who wants to do the HTTP interface?

--- Who wants to do the Bitcoin (multisig) integration?

--- Who wants to do the colored coin stuff?

--- Who wants to do the Bitmessage integration?

--- Who wants to do the systray GUI (I will provide the necessary OT calls.)


I claim systray GUI since I already have code going/posted up.
and will claim HTTP interface.

I can do it all but i don't want to be greedy anyone else can claim the rest I look forward to working with the others that join Smiley
sr. member
Activity: 440
Merit: 251
June 06, 2013, 12:31:24 AM
#27
Tasks.  (Since several people have volunteered, I'd like you to specify tasks you are going to own.)

--- Who wants to do the HTTP interface?

--- Who wants to do the Bitcoin (multisig) integration?

--- Who wants to do the colored coin stuff?

--- Who wants to do the Bitmessage integration?

--- Who wants to do the systray GUI (I will provide the necessary OT calls.)
sr. member
Activity: 440
Merit: 251
June 06, 2013, 12:10:26 AM
#26
There have been several people popping up to do this project, and I think we can divide the tasks between them.

I have created a new github repository for the project.

The bounty is now up to 63.19 BTC.

sr. member
Activity: 440
Merit: 251
June 06, 2013, 12:03:34 AM
#25
I understand that Bitmessage will be used for service discovery between different OT servers but how these servers will transact between themselves? For instance, the universal currency between Ripple gateways is the XRP. What will be the settlement currency between OT federated servers?

See the protocols described in the pastebins linked from this first post:

https://bitcointalksearch.org/topic/the-holy-grail-i-wish-i-could-kiss-the-author-of-bitmessage-on-his-face-212490

OT servers will not have their own "settlement currency." Using the protocols it's already possible to wire funds between servers and also, BTW itself can serve as a "universal glue." (I don't think having our own "OT currency" is the right solution.)
Pages:
Jump to: