Pages:
Author

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

member
Activity: 64
Merit: 10
(Found 9999 unique addresses with a total balance of 2634744.87612734 XCP)  

Over 0.00000001 XCP are in #4516 address.        +602 address
Over 1.0 XCP are in #3297                               +336        
Over 10.0 XCP are in #2331                              +94              
Over 100.0 XCP are in #1490                            -38              
Over 500.0 XCP are in #1064                             -49            
Over 1000.0 XCP are in #892                             -68            
Over 1500.0 XCP are in #149                             -11          
Over 2500.0 XCP are in #98                                 -3      
Over 5000.0 XCP are in #67                                +4

Total XCP balance have go down 6079.94 XCP.

6 month changes in addresses balances. Looks like peoples aren't really interested buying and holding XCP. Now it is under $80 what need to become over 100 XCP holder and in last 6 month more >100 XCP holders have sold than come in. Four new over 5000 XCP holders maybe have come when transfer burned coins to other address...

6 month ago 101 address have over 50% of coins and now 82 address have >50%.

If someone sell $3000 worth of XCP price drop to under $0.30 per XCP. It is 2% of richest address balance Smiley I think we will see new very low price before anything happen what take price go up.


Blockscan can't show over 9999 address for total address where have been before coins?
legendary
Activity: 1762
Merit: 1011
Mobile counterparty wallet on the bitcoin reddit front page (currently the second entry down): https://www.reddit.com/r/Bitcoin/comments/3phfu9/mobile_counterparty_wallet_delivers_1st/

Interestingly, price keeps falling even after this news / exposure
I guess price of XCP is not a good measurement of CP popularity

This is how crypto works. When good news comes out, the price goes lower. Smiley But, seriously, everything is going down relative to this current Bitcoin pop.
legendary
Activity: 1118
Merit: 1004
Mobile counterparty wallet on the bitcoin reddit front page (currently the second entry down): https://www.reddit.com/r/Bitcoin/comments/3phfu9/mobile_counterparty_wallet_delivers_1st/

Interestingly, price keeps falling even after this news / exposure
I guess price of XCP is not a good measurement of CP popularity
legendary
Activity: 1666
Merit: 1010
he who has the gold makes the rules
An alternative implementation we investigated would have the bitcoin escrowed by the Counterwallet system (or an associated 3rd party system), which would remove the need for users to stay logged into the wallet. However, in our case, this could entail us becoming an "exchange" from a legal perspective, or minimally taking on the risk to store users' BTC, both of which we could not do.


Symbiont would technically take custodianship of the BTC in such an arrangement?

None of that has anything to do with Symbiont (and all of this transpired before Symbiont even existed). In this case, when I say "us", I was talking about "us" as the Counterparty co-founders.


This is really interesting.  So according to your research or the advice you received, simply programming an autonomous and decentralized mechanism such as this makes the programmer a custodian of the funds or at least liable for what happens to them?

That's the thing: such a system is not really "decentralized". The bitcoin would have been essentially held with a 3rd party until the trade completed. Multisig, etc. might be able to be employed, but if you want to remove the need for the user on the BTC side of the trade to "be there" to complete it, then someone else would have to do it for them. This service would just sit on top of the decentralized exchange protocol built into Counterparty, and take the BTC side of the trade for the user offering BTC, removing the responsibility of them having to sticking around to complete the trade.


Which 3rd party would have held the BTC?  Counterparty can not be made to escrow the funds autonomously?

_Someone_ would need to handle the BTC, _only_ in this specific case. Note that this is _only_ the case with BTC, and _only_ if you don't want to place _any_ burden on the user that has the BTC to stick around after they place the order. Basically, Counterparty doesn't have the same degree over escrowing BTC that it does with native assets, for purely technical reasons which have been explained elsewhere.


Have you guys mentioned this to Erik V at Shapeshift?


Not that I recall. You're welcome to, though.

I sent him a msg in skype. 

btw who owns that counterwallet website?
sr. member
Activity: 390
Merit: 254
Counterparty Developer
Mobile counterparty wallet on the bitcoin reddit front page (currently the second entry down): https://www.reddit.com/r/Bitcoin/comments/3phfu9/mobile_counterparty_wallet_delivers_1st/
sr. member
Activity: 390
Merit: 254
Counterparty Developer
An alternative implementation we investigated would have the bitcoin escrowed by the Counterwallet system (or an associated 3rd party system), which would remove the need for users to stay logged into the wallet. However, in our case, this could entail us becoming an "exchange" from a legal perspective, or minimally taking on the risk to store users' BTC, both of which we could not do.


Symbiont would technically take custodianship of the BTC in such an arrangement?

None of that has anything to do with Symbiont (and all of this transpired before Symbiont even existed). In this case, when I say "us", I was talking about "us" as the Counterparty co-founders.


This is really interesting.  So according to your research or the advice you received, simply programming an autonomous and decentralized mechanism such as this makes the programmer a custodian of the funds or at least liable for what happens to them?

That's the thing: such a system is not really "decentralized". The bitcoin would have been essentially held with a 3rd party until the trade completed. Multisig, etc. might be able to be employed, but if you want to remove the need for the user on the BTC side of the trade to "be there" to complete it, then someone else would have to do it for them. This service would just sit on top of the decentralized exchange protocol built into Counterparty, and take the BTC side of the trade for the user offering BTC, removing the responsibility of them having to sticking around to complete the trade.


Which 3rd party would have held the BTC?  Counterparty can not be made to escrow the funds autonomously?

_Someone_ would need to handle the BTC, _only_ in this specific case. Note that this is _only_ the case with BTC, and _only_ if you don't want to place _any_ burden on the user that has the BTC to stick around after they place the order. Basically, Counterparty doesn't have the same degree over escrowing BTC that it does with native assets, for purely technical reasons which have been explained elsewhere.


Have you guys mentioned this to Erik V at Shapeshift?


Not that I recall. You're welcome to, though.
legendary
Activity: 1666
Merit: 1010
he who has the gold makes the rules
An alternative implementation we investigated would have the bitcoin escrowed by the Counterwallet system (or an associated 3rd party system), which would remove the need for users to stay logged into the wallet. However, in our case, this could entail us becoming an "exchange" from a legal perspective, or minimally taking on the risk to store users' BTC, both of which we could not do.


Symbiont would technically take custodianship of the BTC in such an arrangement?

None of that has anything to do with Symbiont (and all of this transpired before Symbiont even existed). In this case, when I say "us", I was talking about "us" as the Counterparty co-founders.


This is really interesting.  So according to your research or the advice you received, simply programming an autonomous and decentralized mechanism such as this makes the programmer a custodian of the funds or at least liable for what happens to them?

That's the thing: such a system is not really "decentralized". The bitcoin would have been essentially held with a 3rd party until the trade completed. Multisig, etc. might be able to be employed, but if you want to remove the need for the user on the BTC side of the trade to "be there" to complete it, then someone else would have to do it for them. This service would just sit on top of the decentralized exchange protocol built into Counterparty, and take the BTC side of the trade for the user offering BTC, removing the responsibility of them having to sticking around to complete the trade.


Which 3rd party would have held the BTC?  Counterparty can not be made to escrow the funds autonomously?

_Someone_ would need to handle the BTC, _only_ in this specific case. Note that this is _only_ the case with BTC, and _only_ if you don't want to place _any_ burden on the user that has the BTC to stick around after they place the order. Basically, Counterparty doesn't have the same degree over escrowing BTC that it does with native assets, for purely technical reasons which have been explained elsewhere.


Have you guys mentioned this to Erik V at Shapeshift?
sr. member
Activity: 390
Merit: 254
Counterparty Developer
An alternative implementation we investigated would have the bitcoin escrowed by the Counterwallet system (or an associated 3rd party system), which would remove the need for users to stay logged into the wallet. However, in our case, this could entail us becoming an "exchange" from a legal perspective, or minimally taking on the risk to store users' BTC, both of which we could not do.


Symbiont would technically take custodianship of the BTC in such an arrangement?

None of that has anything to do with Symbiont (and all of this transpired before Symbiont even existed). In this case, when I say "us", I was talking about "us" as the Counterparty co-founders.


This is really interesting.  So according to your research or the advice you received, simply programming an autonomous and decentralized mechanism such as this makes the programmer a custodian of the funds or at least liable for what happens to them?

That's the thing: such a system is not really "decentralized". The bitcoin would have been essentially held with a 3rd party until the trade completed. Multisig, etc. might be able to be employed, but if you want to remove the need for the user on the BTC side of the trade to "be there" to complete it, then someone else would have to do it for them. This service would just sit on top of the decentralized exchange protocol built into Counterparty, and take the BTC side of the trade for the user offering BTC, removing the responsibility of them having to sticking around to complete the trade.


Which 3rd party would have held the BTC?  Counterparty can not be made to escrow the funds autonomously?

_Someone_ would need to handle the BTC, _only_ in this specific case. Note that this is _only_ the case with BTC, and _only_ if you don't want to place _any_ burden on the user that has the BTC to stick around after they place the order. Basically, Counterparty doesn't have the same degree over escrowing BTC that it does with native assets, for purely technical reasons which have been explained elsewhere.
legendary
Activity: 1372
Merit: 1000
An alternative implementation we investigated would have the bitcoin escrowed by the Counterwallet system (or an associated 3rd party system), which would remove the need for users to stay logged into the wallet. However, in our case, this could entail us becoming an "exchange" from a legal perspective, or minimally taking on the risk to store users' BTC, both of which we could not do.


Symbiont would technically take custodianship of the BTC in such an arrangement?

None of that has anything to do with Symbiont (and all of this transpired before Symbiont even existed). In this case, when I say "us", I was talking about "us" as the Counterparty co-founders.


This is really interesting.  So according to your research or the advice you received, simply programming an autonomous and decentralized mechanism such as this makes the programmer a custodian of the funds or at least liable for what happens to them?

That's the thing: such a system is not really "decentralized". The bitcoin would have been essentially held with a 3rd party until the trade completed. Multisig, etc. might be able to be employed, but if you want to remove the need for the user on the BTC side of the trade to "be there" to complete it, then someone else would have to do it for them. This service would just sit on top of the decentralized exchange protocol built into Counterparty, and take the BTC side of the trade for the user offering BTC, removing the responsibility of them having to sticking around to complete the trade.


Which 3rd party would have held the BTC?  Counterparty can not be made to escrow the funds autonomously?
sr. member
Activity: 432
Merit: 250
BTC-XCP trading on the decentralized exchange is still supported both in the protocol itself and in the command-line client. The functionality was removed from Counterwallet simply because, based on user feedback, it proved to be rather unwieldy. I.e. it required users to stay logged in to complete the trades, which many users didn't/couldn't do, causing liquidity issues and frustrating users on the XCP side of the trade.

I feel the need to emphasize this further, as it is getting mentioned in rumors rather frequently:

BTC-XCP trading still works if you use the command-line client and counterparty-lib: https://github.com/CounterpartyXCP/counterparty-cli


sr. member
Activity: 390
Merit: 254
Counterparty Developer
An alternative implementation we investigated would have the bitcoin escrowed by the Counterwallet system (or an associated 3rd party system), which would remove the need for users to stay logged into the wallet. However, in our case, this could entail us becoming an "exchange" from a legal perspective, or minimally taking on the risk to store users' BTC, both of which we could not do.


Symbiont would technically take custodianship of the BTC in such an arrangement?

None of that has anything to do with Symbiont (and all of this transpired before Symbiont even existed). In this case, when I say "us", I was talking about "us" as the Counterparty co-founders.


This is really interesting.  So according to your research or the advice you received, simply programming an autonomous and decentralized mechanism such as this makes the programmer a custodian of the funds or at least liable for what happens to them?

That's the thing: such a system is not really "decentralized". The bitcoin would have been essentially held with a 3rd party until the trade completed. Multisig, etc. might be able to be employed, but if you want to remove the need for the user on the BTC side of the trade to "be there" to complete it, then someone else would have to do it for them. This service would just sit on top of the decentralized exchange protocol built into Counterparty, and take the BTC side of the trade for the user offering BTC, removing the responsibility of them having to sticking around to complete the trade.

In practice, services like Shapeshift can do simple XCP-BTC exchange today, and Shapeshift supports XCP. Shapeshift just doesn't use the Counterparty decentralized exchange functionality, though.
legendary
Activity: 1372
Merit: 1000
An alternative implementation we investigated would have the bitcoin escrowed by the Counterwallet system (or an associated 3rd party system), which would remove the need for users to stay logged into the wallet. However, in our case, this could entail us becoming an "exchange" from a legal perspective, or minimally taking on the risk to store users' BTC, both of which we could not do.


Symbiont would technically take custodianship of the BTC in such an arrangement?

None of that has anything to do with Symbiont (and all of this transpired before Symbiont even existed). In this case, when I say "us", I was talking about "us" as the Counterparty co-founders.


This is really interesting.  So according to your research or the advice you received, simply programming an autonomous and decentralized mechanism such as this makes the programmer a custodian of the funds or at least liable for what happens to them?
sr. member
Activity: 390
Merit: 254
Counterparty Developer
An alternative implementation we investigated would have the bitcoin escrowed by the Counterwallet system (or an associated 3rd party system), which would remove the need for users to stay logged into the wallet. However, in our case, this could entail us becoming an "exchange" from a legal perspective, or minimally taking on the risk to store users' BTC, both of which we could not do.


Symbiont would technically take custodianship of the BTC in such an arrangement?

None of that has anything to do with Symbiont (and all of this transpired before Symbiont even existed). In this case, when I say "us", I was talking about "us" as the Counterparty co-founders.
legendary
Activity: 1372
Merit: 1000
An alternative implementation we investigated would have the bitcoin escrowed by the Counterwallet system (or an associated 3rd party system), which would remove the need for users to stay logged into the wallet. However, in our case, this could entail us becoming an "exchange" from a legal perspective, or minimally taking on the risk to store users' BTC, both of which we could not do.


Symbiont would technically take custodianship of the BTC in such an arrangement?
sr. member
Activity: 390
Merit: 254
Counterparty Developer
the uncertainty of whether things like data feeds will remain as part of the core XCP protocol, and or whether integration of ETH VM will occur and the former will get deprecated is stopping me from mentioning this technology to some cool projects.

just an FYI


Things like data feeds will remain part of the core XCP protocol. I have never heard anything contrary to that.

ok but some stuff did get deprecated in the past like the btc-xcp function right?  I'm just trying to cover my ass before I tell these people and then bam! 6 months later there's an End of Life announcement

It's fun to hear about this kind of real world implementation drama.  Please keep it coming.

BTC-XCP trading on the decentralized exchange is still supported both in the protocol itself and in the command-line client. The functionality was removed from Counterwallet simply because, based on user feedback, it proved to be rather unwieldy. I.e. it required users to stay logged in to complete the trades, which many users didn't/couldn't do, causing liquidity issues and frustrating users on the XCP side of the trade.

An alternative implementation we investigated would have the bitcoin escrowed by the Counterwallet system (or an associated 3rd party system), which would remove the need for users to stay logged into the wallet. However, in our case, this could entail us becoming an "exchange" from a legal perspective, or minimally taking on the risk to store users' BTC, both of which we could not do. A 3rd party that is willing and able to do something like that could implement a service to make BTC-XCP trades much more frictionless. Decentralized trading of any CP asset to any other CP asset (including XCP) is still supported in Counterwallet and in practice is very slick.
sr. member
Activity: 390
Merit: 254
Counterparty Developer
the uncertainty of whether things like data feeds will remain as part of the core XCP protocol, and or whether integration of ETH VM will occur and the former will get deprecated is stopping me from mentioning this technology to some cool projects.

just an FYI


Things like data feeds will remain part of the core XCP protocol. I have never heard anything contrary to that.

ok but some stuff did get deprecated in the past like the btc-xcp function right?  I'm just trying to cover my ass before I tell these people and then bam! 6 months later there's an End of Life announcement

We wouldn't consider EOLing something in the protocol today that had any significant degree of use, I don't think. Data feeds/broadcasts fit that picture.
hero member
Activity: 647
Merit: 510
Counterpartying
the uncertainty of whether things like data feeds will remain as part of the core XCP protocol, and or whether integration of ETH VM will occur and the former will get deprecated is stopping me from mentioning this technology to some cool projects.

just an FYI


Things like data feeds will remain part of the core XCP protocol. I have never heard anything contrary to that.

ok but some stuff did get deprecated in the past like the btc-xcp function right?  I'm just trying to cover my ass before I tell these people and then bam! 6 months later there's an End of Life announcement

You can always email Counterparty and ask. That would be a pretty quick way to get up-to-date information.
legendary
Activity: 1372
Merit: 1000
the uncertainty of whether things like data feeds will remain as part of the core XCP protocol, and or whether integration of ETH VM will occur and the former will get deprecated is stopping me from mentioning this technology to some cool projects.

just an FYI


Things like data feeds will remain part of the core XCP protocol. I have never heard anything contrary to that.

ok but some stuff did get deprecated in the past like the btc-xcp function right?  I'm just trying to cover my ass before I tell these people and then bam! 6 months later there's an End of Life announcement

It's fun to hear about this kind of real world implementation drama.  Please keep it coming.
legendary
Activity: 1666
Merit: 1010
he who has the gold makes the rules
the uncertainty of whether things like data feeds will remain as part of the core XCP protocol, and or whether integration of ETH VM will occur and the former will get deprecated is stopping me from mentioning this technology to some cool projects.

just an FYI


Things like data feeds will remain part of the core XCP protocol. I have never heard anything contrary to that.

ok but some stuff did get deprecated in the past like the btc-xcp function right?  I'm just trying to cover my ass before I tell these people and then bam! 6 months later there's an End of Life announcement
Pages:
Jump to: