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

Noticing a tick up in <1 BTC burns (the stock analogy would be odd-lot trades) the past few days. Increasing public awareness of the XCP idea?

Right now transaction fees are ~20 cents, and the average (American) vocabulary is approximately 10,000 words, so it would only cost ~$2000 for someone to buy every single asset name - certainly, in any case, all the attractive asset names. The fee has to be large enough to prevent this from happening.

The Counterparty team does not want to implement fees, but the peculiarity of the circumstance makes it necessary. It also follows, however, that every fork will have this same problem, and thus will also have to implement fees.

if you put in fees, someone will just fork your code and lower the fee

welcome to open source

I am doing it on Win 7 32 bit.

I burned BTC yesterday successfully and thought today I will try out the other features. I am probably doing them wrong. Can you give instructions on how to do under Windows?

I build from the source and encounter the flowing error

On a side note: You need to be running python 3.2 on windows and rebuild from source again. The 3.3 won't work.

Cheers

Are you running from the newest source, from an installer, or what?

If you're running from source, please try an update, then run again and see if that fixes it:
http://counterpartyd-build.readthedocs.org/en/latest/BuildingFromSource.html#id4

If from an installer, please try running from source
http://counterpartyd-build.readthedocs.org/en/latest/BuildingFromSource.html

Are you able to run other counterpartyd commands fine? How are you running the command (i.e. what's the exact thing you type to get that)? What OS/arch?

We would need more information here to be helpful.

Yep.

can someone answer me this question? - my bitcoind is crashing all the time and I will probably not have time before the end of burning to fix it. so I want to keep them in the blockchain.info

Getting this while trying to get balance.

    from prettytable import PrettyTable
ImportError: No module named prettytable

I got the same problem.  @Devs  I need help, thanks in advance

If it's set to expire then just pay the XCP fee before the date. Bitcoin doesn't function if no one mines so everyone pays miner fees. If you're running a business and you can't pay the registration fee or whatever fee then you're not really running a business anymore. It's really no different. If you stop paying for your website fees or anything else then it goes down. Businesses will always pay the XCP fee and if its a currency not run by a business then someone will pay the fee.

That and also credit or redeemable assets have to expire by design. If they don't expire then how do you offer credit coups? You can't.



A subscription function could allow for recurring payments. You would subscribe to a feed and it would pay the fee on a recurring basis. You would subscribe and it would automatically pay. Of course you would have to set the maximum fee you're willing to pay in total, but once that is set then it could be automatic. I really don't think it's a big deal.

nLockTime right? You can send your fee payments into the future. So you could pay for your future fees by subscribing in such a way so that you pay it into the future up to a maximum amount and time. If my understanding is right it would even be something which could be seen on the blockchain. The money would just be released at a fixed rate so that you could pay the fees for years in advance.

And also if it's registered on the blockchain for example, if you pay your fees into the future while fees are low, it might be possible to do it in a way where even if the fees are raised you've already paid 5 years in advance. But people who didn't pay into the future, if the fees raise their prices are not locked in.

Then we could encourage people to pay 5 years in advance to lock in those cheap fee rates. People who don't do that will just pay whatever the fee rates are, this would encourage people to pay years in advance and create stability.

I'm still waiting to see that.
1 time command/transmission, y$ set to be send in 2~48 time (automatically), over t time.

I have a pubkey with x.
I wish x/12 to be send to someone else every month (nb equi block).

edit: doing it manually every month will be a real pain + forget = business destroyed

Then perhaps requiring an upkeep fee, as one does with the domains, say X XCP per month?
Eventually the squater will find it uneconomical to hold all these assets for nothing.

Create a finite lifespan for asset appear to be an horrible idea to me...
Imagine if your BTC suddenly disappeared.
Or that you spend a lot of time for promotion, succeed to have an awesome dividend system to many client and suddenly all your client holding disappear.
I can hardly imagine something better to destroy your business.

Perhaps a mix of 1 and 2 can be a good idea, both creating assets locally and pushing/paying when needed, and allowing fair chance others to re-register the asset in future.

A thought I had about the future danger of BTC miners blocking the XCP transactions - what if we provide XCP as miners fee?
The fee might be relational to what BTC currently takes (0.0001) vs XCP total volume, 0.00001 for example.

Provided XCP raises in value, this will motivate miners to allow it through their systems and get paid for that, in addition to regular BTC fee.

Several potential ways:

1. Make all of them local and provide a way to globalize them (my suggestion)
2. Give them a finite lifespan that causes them to expire now/some time in the future (luckybit's suggestion)
3. Invalidate all of them and start over (the brute force solution) - personally I don't recommend this
4. Don't do anything (it's only 5 XCP...)
5. Retroactively charge 5 XCP (really don't recommend this)

The workable solutions I bolded.

Any others?

Awesome!

Any way to clean up all the already squatted assets?