Bitcoin Forum
November 08, 2024, 07:27:54 PM *
News: Latest Bitcoin Core release: 28.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 [18] 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 ... 661 »
  Print  
Author Topic: [ANN][XCP] Counterparty - Pioneering Peer-to-Peer Finance - Official Thread  (Read 1276762 times)
This is a self-moderated topic. If you do not want to be moderated by the person who started this topic, create a new topic.
reader31
Full Member
***
Offline Offline

Activity: 221
Merit: 100


View Profile
January 05, 2014, 11:36:30 PM
 #341

There we go...the first hate post! took only 3 days! Smiley

BldSwtTrs
Legendary
*
Offline Offline

Activity: 861
Merit: 1010


View Profile
January 05, 2014, 11:40:23 PM
Last edit: September 20, 2017, 09:03:48 AM by BldSwtTrs
Merited by nutildah (5)
 #342

OK I give up trying to install counterpartyd, I am too stupid to do that.

I just make a test transaction using blockchain.info : 003ecc99cb3533920f2ce26136605b5b051245ac1d823f559d7d1a27c37b642f

Can someone with counterpartyd check if I have the XCP before I burn more BTC.
panonym
Sr. Member
****
Offline Offline

Activity: 266
Merit: 250

Help and Love one another ♥


View Profile
January 05, 2014, 11:46:33 PM
 #343

feed-issuers have the added incentive of developing a reputation: the more often they maintain their feeds to the satisfaction of those who are betting, the more trusted they will become, and hence the more often betters will bet on feeds issued by them.
This betting system seem to rely on trust... That's a problem to me.
We can bet anything, but the feed output is under control of a single one.
Nothing stop him to feed the opposite of the true result of the bet.
Do I miss something?

OK I give up trying to install counterpartyd, I am too stupid to do that.
Don't lower yourself Wink
Hard at the beginning, but can work. [not done yet on my side, hopefully soon]
Start by adding txindex=1 in your bitcoin.conf, then do a bitcoind -reindex (this will take you +12h, that you will anyway need to do in the future to have full potential of your XCP)
cityglut
Full Member
***
Offline Offline

Activity: 216
Merit: 100


View Profile
January 06, 2014, 12:23:32 AM
 #344

feed-issuers have the added incentive of developing a reputation: the more often they maintain their feeds to the satisfaction of those who are betting, the more trusted they will become, and hence the more often betters will bet on feeds issued by them.
This betting system seem to rely on trust... That's a problem to me.
We can bet anything, but the feed output is under control of a single one.
Nothing stop him to feed the opposite of the true result of the bet.
Do I miss something?


'Trust' is a misleading word. Consider the situation from a feed-operator's point of view: For the most part, the actual data that a feed operator is publishing will be extremely easy to find outside of Counterparty, and consequently, whether a feed-operator has tampered with the data will be readily verifiable. Users will then stop betting on feeds published by such a feed-operator.

Betting in Counterparty doesn't depend on feed-operators being honest, it depends on them being rational.

Now one could argue that a feed operator can create arbitrarily many addresses, and consequently can continue publishing faulty under new identities. In my opinion, however, this is not a real concern, given how I see Counterparty developing. Namely: one will discover feed-operators outside of the blockchain (either through forum threads or external websites, or whatever), see which public addresses they says are theirs, and bet accordingly. This further increases the utility of reputation within Counterparty, and hence reduces the risk of being scammed.
cityglut
Full Member
***
Offline Offline

Activity: 216
Merit: 100


View Profile
January 06, 2014, 12:48:20 AM
 #345


Let's say I want to put out a broadcast with a fee of .01 (or 1% of the bets made on the broadcast) - it would look like this:

python3 counterpartyd.py --rpc-password=PASSWORD broadcast --from=ADDRESS --text=TEXT --fee-multiplier=.01

The text of a broadcast is a string. If you want to publish a value later on, then the syntax is:

python3 counterpartyd.py --rpc-password=PASSWORD broadcast --from=ADDRESS --text=TEXT --fee-multiplier=.01 --value=VALUE

Does that help?

I don't understand why there are two commands nor what they do.

For the first command, is the fee of 0.01 something I have to pay?

For the second command, do I need to pay for each update I make?  If so, do I pay in BTC or XCP?   Finally, where is this information stored?  In the bitcoin block chain OR does counterpart have its own block chain?

Thanks.

Anyone?

The first command is what people are betting on, and the second command, which includes the 'value' function publishes the actual outcome of the bet, and hence determines which user won the bet.
PhantomPhreak (OP)
Sr. Member
****
Offline Offline

Activity: 476
Merit: 300

Counterparty Chief Scientist and Co-Founder


View Profile
January 06, 2014, 01:00:26 AM
 #346


Let's say I want to put out a broadcast with a fee of .01 (or 1% of the bets made on the broadcast) - it would look like this:

python3 counterpartyd.py --rpc-password=PASSWORD broadcast --from=ADDRESS --text=TEXT --fee-multiplier=.01

The text of a broadcast is a string. If you want to publish a value later on, then the syntax is:

python3 counterpartyd.py --rpc-password=PASSWORD broadcast --from=ADDRESS --text=TEXT --fee-multiplier=.01 --value=VALUE

Does that help?

I don't understand why there are two commands nor what they do.

For the first command, is the fee of 0.01 something I have to pay?

For the second command, do I need to pay for each update I make?  If so, do I pay in BTC or XCP?   Finally, where is this information stored?  In the bitcoin block chain OR does counterpart have its own block chain?

Thanks.

Anyone?

The first command is just a limiting case of the second command. fee_multiplier is the fraction of every bet made on your feed that you get paid in fees. All of the data are imbedded in the OP_RETURN output.
xibeijan
Legendary
*
Offline Offline

Activity: 1232
Merit: 1001


View Profile
January 06, 2014, 01:02:36 AM
 #347


Let's say I want to put out a broadcast with a fee of .01 (or 1% of the bets made on the broadcast) - it would look like this:

python3 counterpartyd.py --rpc-password=PASSWORD broadcast --from=ADDRESS --text=TEXT --fee-multiplier=.01

The text of a broadcast is a string. If you want to publish a value later on, then the syntax is:

python3 counterpartyd.py --rpc-password=PASSWORD broadcast --from=ADDRESS --text=TEXT --fee-multiplier=.01 --value=VALUE

Does that help?

I don't understand why there are two commands nor what they do.

For the first command, is the fee of 0.01 something I have to pay?

For the second command, do I need to pay for each update I make?  If so, do I pay in BTC or XCP?   Finally, where is this information stored?  In the bitcoin block chain OR does counterpart have its own block chain?

Thanks.

No, the fee is something those who are betting on your feed have to pay. The fee is basically meant to incentivize the issuer of the feed to maintain the integrity of the feed (both updating it regularly and not tampering with it). In my opinion, feed-issuers have the added incentive of developing a reputation: the more often they maintain their feeds to the satisfaction of those who are betting, the more trusted they will become, and hence the more often betters will bet on feeds issued by them.

You have to pay the standard Bitcoin fee for making a transaction each time you update your feed, yes.

The information is stored in the Blockchain. Counterparty does not have its own blockchain; Counterparty transactions are made on the Bitcoin blockchain.

Thanks to all.

Is the fee they pay for using the feed in BTC or XCP?  Is the standard Bitcoin fee I have to pay the min bitcoin TX fee of 0.0001 BTC?

So, when I transfer XCP I need to pay a 0.0001 BTC tx fee?  So, while using CounterParty I am spending both XCP and BTC?

Can I switch back and forth between the mainnet and testnet (bitcoind and counterpartyd) without causing any problems?  Anything I need to watch out for?

Are feed's names (i.e. TEXT) owned by those who initialise/buy them?  Or can anyone post to any feed?

Notable projects 2019: Semux, Dero, Wagerr, BEAM
kdrop22
Full Member
***
Offline Offline

Activity: 238
Merit: 100


View Profile
January 06, 2014, 01:10:50 AM
 #348

Would someone be kind enough to check if my test transaction is correct.
https://blockchain.info/tx/3db7d791ff30c8ddbd82fa8bb04c42842e8f3aa793bb0b81bfb40822629e26a3
panonym
Sr. Member
****
Offline Offline

Activity: 266
Merit: 250

Help and Love one another ♥


View Profile
January 06, 2014, 01:13:23 AM
 #349

I don't get this betting system.

Let say I wish to bet that at block xxxx BTC will be have a value superior to now.
Or XCT/BTC value in 24h will be higher.
Or that the last 8 binary digit of the BTC block xxxx will be over 11110000.
This result can easily be proven when then time comes.
Yet bet function doesn't appear to be descentralized.
As someone has to push feed as I understand.
There is a trust matter about the feeder publishing the correct result (result that will split the reward accordingly).

That, or you have a totally other idea about betting.
That is not compatible with my example.
PhantomPhreak (OP)
Sr. Member
****
Offline Offline

Activity: 476
Merit: 300

Counterparty Chief Scientist and Co-Founder


View Profile
January 06, 2014, 01:13:57 AM
 #350

I just make a test transaction using blockchain.info : 003ecc99cb3533920f2ce26136605b5b051245acfd823f559d7d1a27c37b642f

Can someone with counterpartyd check if I have the XCP before I burn more BTC.

It looks good. You burned .01 BTC and got 14.58363636 XCP in return.



Let's say I want to put out a broadcast with a fee of .01 (or 1% of the bets made on the broadcast) - it would look like this:

python3 counterpartyd.py --rpc-password=PASSWORD broadcast --from=ADDRESS --text=TEXT --fee-multiplier=.01

The text of a broadcast is a string. If you want to publish a value later on, then the syntax is:

python3 counterpartyd.py --rpc-password=PASSWORD broadcast --from=ADDRESS --text=TEXT --fee-multiplier=.01 --value=VALUE

Does that help?

I don't understand why there are two commands nor what they do.

For the first command, is the fee of 0.01 something I have to pay?

For the second command, do I need to pay for each update I make?  If so, do I pay in BTC or XCP?   Finally, where is this information stored?  In the bitcoin block chain OR does counterpart have its own block chain?

Thanks.

No, the fee is something those who are betting on your feed have to pay. The fee is basically meant to incentivize the issuer of the feed to maintain the integrity of the feed (both updating it regularly and not tampering with it). In my opinion, feed-issuers have the added incentive of developing a reputation: the more often they maintain their feeds to the satisfaction of those who are betting, the more trusted they will become, and hence the more often betters will bet on feeds issued by them.

You have to pay the standard Bitcoin fee for making a transaction each time you update your feed, yes.

The information is stored in the Blockchain. Counterparty does not have its own blockchain; Counterparty transactions are made on the Bitcoin blockchain.

Thanks to all.

Is the fee they pay for using the feed in BTC or XCP?  Is the standard Bitcoin fee I have to pay the min bitcoin TX fee of 0.0001 BTC?

So, when I transfer XCP I need to pay a 0.0001 BTC tx fee?  So, while using CounterParty I am spending both XCP and BTC?

Can I switch back and forth between the mainnet and testnet (bitcoind and counterpartyd) without causing any problems?  Anything I need to watch out for?

The fee paid to a feed operator is in XCP. It is a fraction of the bet, which is in XCP. Yes, the BTC fee for every transaction is .0001 BTC.

Simply transferring XCP, for example, does not incur an XCP fee.

Yes. The two should run together without a hiccup.
BldSwtTrs
Legendary
*
Offline Offline

Activity: 861
Merit: 1010


View Profile
January 06, 2014, 01:16:20 AM
 #351

God, why I have this message :
Code:
Traceback (most recent call last):
  File "C:\counterpartyd_build\dist\counterpartyd\counterpartyd.py", line 413, i
n <module>
    util.bitcoind_check(db)
  File "C:\counterpartyd_build\dist\counterpartyd\lib\util.py", line 19, in bitc
oind_check
    block_count = bitcoin.rpc('getblockcount', [])
  File "C:\counterpartyd_build\dist\counterpartyd\lib\bitcoin.py", line 51, in r
pc
    raise exceptions.BitcoindRPCError('Cannot communicate with Bitcoind. (counte
rpartyd is set to run on {}, is Bitcoind?)'.format(network))
lib.exceptions.BitcoindRPCError: Cannot communicate with Bitcoind. (counterparty
d is set to run on mainnet, is Bitcoind?)

C:\counterparty_build\counterpartyd.conf :
Quote
[Default]
rpc-connect=localhost
rpc-port=8332
rpc-user=rpc
rpc-password=password

C:\Program Files (x86)\bitcoin\bitcoin.conf :
Quote
rpcuser=rpc
rpcpassword=password
server=1
daemon=1
txindex=1
panonym
Sr. Member
****
Offline Offline

Activity: 266
Merit: 250

Help and Love one another ♥


View Profile
January 06, 2014, 01:17:39 AM
 #352

So every transaction of XCP or asset will have a 0.0001 BTC fee.
0.001 BTC fee is ONLY for burning through counterpartyd.
Then why using your soft to burn if it cost me 9x less using blockchain.info ?
Much more easy, cheaper, almost unfair.
xibeijan
Legendary
*
Offline Offline

Activity: 1232
Merit: 1001


View Profile
January 06, 2014, 01:23:26 AM
 #353

Simply transferring XCP, for example, does not incur an XCP fee.

How is this possible, if the XCP transactions need to be written into the bitcoin block chain?


Are feed's names (i.e. TEXT) owned by those who initialise/buy them?  Or can anyone post to any feed?

Notable projects 2019: Semux, Dero, Wagerr, BEAM
cityglut
Full Member
***
Offline Offline

Activity: 216
Merit: 100


View Profile
January 06, 2014, 01:24:33 AM
 #354

So every transaction of XCP or asset will have a 0.0001 BTC fee.
0.001 BTC fee is ONLY for burning through counterpartyd.
Then why using your soft to burn if it cost me 9x less using blockchain.info ?
Much more easy, cheaper, almost unfair.

Where did you see that it cost .001 BTC to burn through counterpartyd?

The fee for all XCP transactions is the same.
panonym
Sr. Member
****
Offline Offline

Activity: 266
Merit: 250

Help and Love one another ♥


View Profile
January 06, 2014, 01:28:26 AM
 #355

So every transaction of XCP or asset will have a 0.0001 BTC fee.
0.001 BTC fee is ONLY for burning through counterpartyd.
Then why using your soft to burn if it cost me 9x less using blockchain.info ?
Much more easy, cheaper, almost unfair.

Where did you see that it cost .001 BTC to burn through counterpartyd?

The fee for all XCP transactions is the same.

An old post. As transaction <1kB fee was 10 time higher.
Miss read/remember?
So every transaction of XCP or asset just require the standard 0.0001 BTC fee?
PhantomPhreak (OP)
Sr. Member
****
Offline Offline

Activity: 476
Merit: 300

Counterparty Chief Scientist and Co-Founder


View Profile
January 06, 2014, 01:29:50 AM
 #356

Are feed's names (i.e. TEXT) owned by those who initialise/buy them?  Or can anyone post to any feed?

A feed is a series of broadcasts from a given address.


So every transaction of XCP or asset just require the standard 0.0001 BTC fee?

Correct.
xibeijan
Legendary
*
Offline Offline

Activity: 1232
Merit: 1001


View Profile
January 06, 2014, 01:32:02 AM
Last edit: January 06, 2014, 01:44:20 AM by xibeijan
 #357

Are feed's names (i.e. TEXT) owned by those who initialise/buy them?  Or can anyone post to any feed?

A feed is a series of broadcasts from a given address.

So, users just subscribe to a bitcoin address?  How do they know what it's about?

Where does the --text=TEXT parameter come in?

I can run two bitcoind's at the same time using the -datadir option.  Can I also run two counterpartyd's at the same time?  I'd like to have testnet and mainnet running at same time, rather than switching back and forth.

Notable projects 2019: Semux, Dero, Wagerr, BEAM
PhantomPhreak (OP)
Sr. Member
****
Offline Offline

Activity: 476
Merit: 300

Counterparty Chief Scientist and Co-Founder


View Profile
January 06, 2014, 01:42:12 AM
 #358

Are feed's names (i.e. TEXT) owned by those who initialise/buy them?  Or can anyone post to any feed?

A feed is a series of broadcasts from a given address.

So, users just subscribe to a bitcoin address?  How do they know what it's about?

Where does the --text=TEXT parameter come in?

I don't know about 'subscribe', but yes. They know what it's about by the --text=TEXT parameter.
panonym
Sr. Member
****
Offline Offline

Activity: 266
Merit: 250

Help and Love one another ♥


View Profile
January 06, 2014, 01:44:21 AM
 #359

'feeling more and more question will be skipped as the message speed increase over time.
But still get a few, good.

I'm in for the XCP/BTC, asset/BTC, asset/XCP descentralized exchange.
All the rest is obscure.

A copypast of what I wrote in another project post: (which could give HUGE succes to your project)
I wish to see a descentralized email-like system, where I can give priority-reading/answering to the people that pay to contact me.
Free or minimal fee goes into 1 folder, a subalias or something.
Others are categorized between x$ & y$. Or classified by amount max to min.
'Details, but I think you get the idea.
Have you the skill to develop such a system?  'possibility to include it somehow in counterpartyd?
xibeijan
Legendary
*
Offline Offline

Activity: 1232
Merit: 1001


View Profile
January 06, 2014, 01:45:10 AM
 #360

I can run two bitcoind's at the same time using the -datadir option.  Can I also run two counterpartyd's at the same time?  I'd like to have testnet and mainnet running at same time, rather than switching back and forth.

Notable projects 2019: Semux, Dero, Wagerr, BEAM
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 [18] 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 ... 661 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!