Page 2 of 5

Re: RPC interface / raw transactions for safe name trading

Posted: Wed Apr 09, 2014 9:06 am
by phelix
domob wrote:I think you are mistaken, as far as I understand. Each individual output specifies the script necessary
to redeem it (i. e., the address). So the name output as well as the coin output specify explicitly individual addresses -
it is already like this, except that the coins are always change and usually both addresses belong to the same person.
This is not required, though. I don't see a problem with what you write.
All the better. I missed that the name is specified in the output script itself :roll:

Re: RPC interface / raw transactions for safe name trading

Posted: Mon Apr 28, 2014 7:45 am
by phelix
Is it possible to get the output of a name tx with listunspent? It does not seem to work...

Re: RPC interface / raw transactions for safe name trading

Posted: Mon Apr 28, 2014 9:10 am
by domob
phelix wrote:Is it possible to get the output of a name tx with listunspent? It does not seem to work...
I don't think so. But it should be possible to extend it with an optional argument or something. What do you want it for?

Re: RPC interface / raw transactions for safe name trading

Posted: Wed Apr 30, 2014 3:00 pm
by snailbrain
Definitely namecoin needs name trading.

a Bonus for doing it (i sent this in a PM probably a while back):
When this is done (with a GUI), it should be very simple to modify it for "Share type Trading" using actual names (so it is very basic/simple and easy to understand):

This is an example based on crypto-currency type shares (and was some late night fantasy :) )
We would like to sell 1000 chronoking shares at 100 NMC each, when Chronokings is released, 1 Chronoking Share will = 500 CHR (Chronos).
We create 1000 names:--- sh/chronokings1 to sh/chronokings1000 .(i mentioned this to someone else and they suggested sh/chronokings/1 etc)
We also create sh/chronokings - which has some values like "total shares" and maybe contact/contract details.

The names are then listed for sale in the "Name Trading Client" (or a new tab in current QT) - possibly in "shares tab" - which allows grouping of names based on sh/chronokings values, but uses the same atomic trading for trading names.

Investors then buy the shares at the fixed price, and can also trade them in the names or shares tab, maybe the shares themselves will go up/down in value.
When Chronokings is released, they create a CHR address to receive coins and update their shares name in namecoin (sh/chronokings/43) with their chronokings address.
they then transfer the name (share) to our specified address to cash them in.. we then send the CHR to their address. (alternatively, they can actually be shares in a company, i.e. %)

That is just an example of a use.

Share Atomic Name Trading (?) -
Name trading itself will boost namecoin via speculation for names
Share Trading will boost namecoin, as the shares are traded in NMC.

Apologise I have not much input on the technical side :)

Re: RPC interface / raw transactions for safe name trading

Posted: Thu May 01, 2014 7:11 pm
by phelix
domob wrote:
phelix wrote:Is it possible to get the output of a name tx with listunspent? It does not seem to work...
I don't think so. But it should be possible to extend it with an optional argument or something. What do you want it for?
Well, atomic name trading, done manually or via a script and RPC calls. :mrgreen:

@snailbrain: to some basic extend this works already now: https://github.com/phelixbtc/ncsc

Re: RPC interface / raw transactions for safe name trading

Posted: Fri May 02, 2014 1:56 pm
by snailbrain
phelix wrote:
domob wrote:
phelix wrote:Is it possible to get the output of a name tx with listunspent? It does not seem to work...
I don't think so. But it should be possible to extend it with an optional argument or something. What do you want it for?
Well, atomic name trading, done manually or via a script and RPC calls. :mrgreen:

@snailbrain: to some basic extend this works already now: https://github.com/phelixbtc/ncsc
need idiot proof gui :)

Re: RPC interface / raw transactions for safe name trading

Posted: Tue May 06, 2014 5:55 am
by domob
BTW, what about merging my pull requests - do you think I need to polish them further? I'd like to get them into the code before continuing with the work here. (Because I don't want to have too many open patches at the same time.)

Re: RPC interface / raw transactions for safe name trading

Posted: Tue May 06, 2014 10:50 am
by phelix
domob wrote:BTW, what about merging my pull requests - do you think I need to polish them further? I'd like to get them into the code before continuing with the work here. (Because I don't want to have too many open patches at the same time.)
I suggest we merge all the latest changes into a beta branch and do a release candidate.

Re: RPC interface / raw transactions for safe name trading

Posted: Wed May 07, 2014 6:12 am
by domob
phelix wrote:
domob wrote:BTW, what about merging my pull requests - do you think I need to polish them further? I'd like to get them into the code before continuing with the work here. (Because I don't want to have too many open patches at the same time.)
I suggest we merge all the latest changes into a beta branch and do a release candidate.
IMHO, the "master" branch should contain the "bleeding edge" (except unfinished / completely untested things under development). If we want to prepare a stable release without the latest changes, I suggest to create a "release candidate" branch instead and merge the changes (after reasonable testing) to master instead. The master branch should be understood as ongoing development (like your idea of a "beta" branch) and not as the stable version. I believe this is the common strategy when developing projects.

Re: RPC interface / raw transactions for safe name trading

Posted: Thu May 08, 2014 4:47 pm
by phelix
ok.

Especially for noobs it can be confusing that github defaults to some bleeding edge version. What about creating a release branch and make that the default branch? We can then tag the release branch with versions.