Topic: [ANN][XCP] Counterparty - Pioneering Peer-to-Peer Finance - Official Thread - page 577. (Read 1276936 times)

That error message sure isn't very helpful! The problem is that deadlines are specified in actual times, not block numbers, and moreover in human-readable formats, such as 'Mon Feb  3 10:00:00 UTC 2014'. (I actually haven't figured out myself exactly what datetime will accept, yet... it won't take Unix time, for no reason.)

The expiration is the maximum number of blocks that you want your bet to be available to be matched for.

Hi,

Need more guidance on how to actually use the bet/feed system.

What I think I'm trying to do:
Enter a bet from 1Fz5idgemYfsszRMmaQNd2Anvm2JytAoU (my XCP account) to feed 1QBPsB2ea61vWTNA9nGUhaHqPQB4SXF4fN (super bowl feed) to bet 1 XCP that Denver (2) will win at or before block 290000 (random estimate in future).

What I entered:

C:\counterpartyd>python counterpartyd.py bet --from 1Fz5idgemYfsszRMmaQNd2Anvm2J
ytAoU --feed-address 1QBPsB2ea61vWTNA9nGUhaHqPQB4SXF4fN --bet-type Equal --deadl
ine 290000 --wager 1 --counterwager 1 --target-value 2 --expiration 2
Traceback (most recent call last):
  File "counterpartyd.py", line 564, in
    deadline = round(datetime.timestamp(dateutil.parser.parse(args.deadline)))
AttributeError: type object 'datetime.datetime' has no attribute 'timestamp'

Don't know what to put in expiration because anything is giving me errors.

Someone is burning big.. Like 30 or so btc in the last 2 blocks.  

Folks, be wary of trusting blockscan.com because it won't always be correct.

Hmm. I'm not having that problem. Is anyone else? What platform are you on, BiggestFish?

Fun, I'll try to enter a bet now.

It looks as though the blockchain reorganisation made it such that your first order expired just before it was matched.

Yes but it doesn't show up in counterpartyd wallet.
I removed the database files and let server recreate them and still no XCP at 1M3wvBm31kVJkzA5A2KwhWws7YGq9AYsKv.

That's funny. I'll try to fix that.



Those addresses The second two addresses in each escrow are the fake addresses in which the Counterparty data is stored. Those 0.0001086 BTC return to you in a multi-sig 1-of-3 output.

Maybe I'm wrong but I think that there is a relatively easy way to do this:

Say Alice is a Counterparty user and Bob is a NXT user. Alice and Bob want to get their respective tokens "into" each others systems. They can set up a multisig address (2 of 2) on each system to which they both have 1 of the keys. They can both add some amount (say $10,000 worth) of their tokens into the multisig addresses. So now the NXT address has say 20,000 NXT and the Counterparty address has 4,000 XCP. Both Alice and Bob can define the appropriate assets/colored coins. They are effectively performing escrow for each other. In this manner you are actually "backing" NXT assets with NXT and XCP assets with XCP.

Of course there are all sorts of potential issues with this such as - how do you know that Alice and Bob aren't the same person. In the long-term that doesn't matter because both Alice and Bob will be DACs. You could technically trade between an "XCP colored NXT" and an "NXT colored XCP" via "Alice and Bob".

So there's an answer to your earlier question James: The most valuable DACs? - How about one which facilitates interoperability between decentralized exchanges.

Another neat way of doing this would be to extend the Counterparty Protocol across both Bitcoin and NXT (using the arbitrary message system)! This would mean the NXT system could have colored coins on top of colored coins. "This coin represents a Counterparty token which represents my deeds to this house".

Let's do this!
It will be a huge boost for both projects, they share many things in common.

James,

Thank you for your interest in Counterparty!

Getting NXT listed within Counterparty would be a bit tricky. Even if someone created asset REALNXT in Counterparty and sold them, he would have to 'back' REALNXT with NXT, and make a sort-of IOU out of it, such that REALNXT can be redeemed for NXT. The mechanism by which the latter happens will have to be determined by the issuer of REALNXT, of course, though I do have some ideas as to how this could be done.

It would be great if XCP could be sold on NXT Asset Exchange, though I do not know whether this is possible.

If you are interested in further discussing things further, please PM me or have someone from the NXT community PM me.

Have we irc channel already or can we open? Im in #xcp and #xcpcoin

Generally Agree - I am planning of Donating ~10% of my XCP to created Bounties.

I cannot add much value regarding technical development. But as a financial economist I will probably add a paper why XCP is superior regarding superstructure to Mastercoin, probably Bitshares and Ethereum. Counterparty almost fullfills one of the core axioms of economics, which is brutally important to functionality of financial markets, the atomic hypothesis.

Cityglut has posted what we hope (with potential tweaks from the community) can become the guiding principles behind Counterparty. Most significantly, this project is as much the community's project as it is ours. Counterparty aims to follow the model used by Satoshi: Introduce innovative technology, and let a community form around it.

That is our goal here. Counterparty is what we all will make of it, and the initiative shown by you guys has been great so far. Let's keep building on that.

Regarding Counterparty's development, we've come up with what we think are good guidelines specifying the limited role of the core Counterparty team vs. that of the Counterparty community at large. We'd love for members of the community to review and comment on this as we see this statement, once approved by our team and the majority of the community, as serving as the guiding principles of the Counterparty project as a whole.

Counterparty Project Principles

Members of the community have burned or otherwise invested their funds into the success of the project.  The core development team will produce and maintain the reference client(s), official website and protocol specification. The community will self-organize and produce products, services, and businesses around these tools, as well as their own.

As a member of the community, you are encouraged to:

• Freely create useful applications around Counterparty technology and be compensated accordingly as people use your product or service.
• Be proactive and take initiative around the Counterparty protocol and in the community which will collectively be evidenced by a rising XCP value.
• Promote innovation by cooperating, sharing and collaborating with other community members.

If you only see that once, that shouldn't be a problem. The counterpartyd zmq functionality will probably be coming out in the next day or two anyhow, due to reliability issues of a real-time feed (i.e. missed packets, out of order data) as opposed to polling the API.

Ok. I've renamed the purge to reparse in blocks.py. Lets see if this holds...

I am also seeing the error "\xd8MQ publisher not active. Sleeping for 0.25 seconds. (Try 1/12)"....'

cheers

Yeah, I was just about to respond to your PM about that. I renamed the 'purge' function 'reparse'. I probably won't be able to push the commit which fixes this problem till Monday, however ('cuz I bundled it up with stuff that isn't ready yet). Feel free to rename that function call yourself.

Hi

There is an issue with the latest develop branch GIT. It will throw an exception everytime a block reorganization is detected


Status: Blockchain reorganisation at block 283588.
Traceback (most recent call last):
  File "C:\counterpartyd_build\dist\counterpartyd\counterpartyd.py", line 715, in
    blocks.follow(db)
  File "C:\counterpartyd_build\dist\counterpartyd\lib\blocks.py", line 613, in follow
    block_index = reorg(db)
  File "C:\counterpartyd_build\dist\counterpartyd\lib\blocks.py", line 509, in reorg
    purge(db, quiet=True)
NameError: global name 'purge' is not defined