|
the_game1224
|
 |
October 03, 2014, 03:02:34 PM |
|
Happy Friday everyone! Haven't been on here as much lately and was just curious what the XC team members are working on right now? Sort of like what was listed in the old daily updates. Thanks and I hope everyone has a good weekend  |
|
|
|
|
|
|
|
KimmyF
|
|
October 03, 2014, 03:23:31 PM |
|
Ok, there will be limitations in my block explorer. Just finished a dynamic caching module in the back-end because some transactions where just to much for a browser to handle. eg: if one or more outputs are not spend i let the browser render the graph, if all outputs are spend the svg is served without the need for any end-user processing. Simply because unspend outputs can change the graph & i needed some simple & quick caching able to run in the cloud. But visualizing seemingly simple things can give crazy results, check this out: Thats a 6x times zoom in  ( https://chainz.cryptoid.info/xc/tx.dws?f14319b3154e5f6f1c0c46af46159d46308abb47b4e86710af23d8885e81d964.htm) Just someone scraping together about 300 seperate inputs into a single tx-out without time-frame, this has nothing to do with anon (no multisigs) Funny to see how (only for XC) regulair Anon transactions are more easy to handle by a browser (visual tech wise) and how some people had concerns about bloat because of the XCoinshuffle thats part of the anon:D Overall ... am almost there ... |
|
|
|
|
|
sugarboy321
|
|
October 03, 2014, 03:32:03 PM |
|
Ok, there will be limitations in my block explorer.
Just finished a dynamic caching module in the back-end because some transactions where just to much for a browser to handle.
eg: if one or more outputs are not spend i let the browser render the graph, if all outputs are spend the svg is served without the need for any end-user processing. Simply because unspend outputs can change the graph & i needed some simple & quick caching able to run in the cloud.
But visualizing seemingly simple things can give crazy results, check this out: Thats a 6x times zoom in
Just someone scraping together about 300 seperate inputs into a single tx-out without time-frame, this has nothing to do with anon (no multisigs)
Funny to see how (only for XC) regulair Anon transactions are more easy to handle by a browser (visual tech wise) and how some people had concerns about bloat because of the XCoinshuffle thats part of the anon:D
Overall ... am almost there ...
It's Beautiful.... |
|
|
|
|
|
cryptico
|
|
October 03, 2014, 03:33:12 PM |
|
Dan that is a Rev 3 feature in the road map sneaky you! |
|
|
|
|
infinitechaos
|
|
October 03, 2014, 03:39:15 PM |
|
I feel so out of the loop. I haven't been able to try XChat at all yet because I'm on a Mac.  |
|
|
|
|
Longenecker
|
|
October 03, 2014, 03:40:38 PM |
|
Ok, there will be limitations in my block explorer. Just finished a dynamic caching module in the back-end because some transactions where just to much for a browser to handle. eg: if one or more outputs are not spend i let the browser render the graph, if all outputs are spend the svg is served without the need for any end-user processing. Simply because unspend outputs can change the graph & i needed some simple & quick caching able to run in the cloud. But visualizing seemingly simple things can give crazy results, check this out: Thats a 6x times zoom in [img snip] ( https://chainz.cryptoid.info/xc/tx.dws?f14319b3154e5f6f1c0c46af46159d46308abb47b4e86710af23d8885e81d964.htm) Just someone scraping together about 300 seperate inputs into a single tx-out without time-frame, this has nothing to do with anon (no multisigs) Funny to see how (only for XC) regulair Anon transactions are more easy to handle by a browser (visual tech wise) and how some people had concerns about bloat because of the XCoinshuffle thats part of the anon:D Overall ... am almost there ... Looks amazing! Wow, I can't wait for this to go live! |
|
|
|
|
|
atcsecure
|
|
October 03, 2014, 03:43:16 PM |
|
Dan that is a Rev 3 feature in the road map sneaky you! The requests for group chat drove this feature to the top of the list!!!! On a side note, I've been contacted by several dev's on a various list of projects - just wanted to keep the community in the loop * Ruble Code review * Britcoin - license rev1 mixer code * Utility Coin - collaboration * Supernet - collaboration Dan |
Join the revolution - XC - Decentralized Trustless Multi-Node Private Transactions
|
|
|
|
KimmyF
|
|
October 03, 2014, 03:46:03 PM |
|
Dan, After the last time i asked did some research and now understand the need for re-entering the public key for Xchat. But at the same time i feel this will limit the adaptation of XChat by non tech/altcoin people, just because its just a lot of hassle & they have no idea what a private key is. For many i know a XC address looks crazy enough. Is there some (anon related) reason for not letting the wallet discover the public key by itself before encrypting the channel or do you think there is some way to build this tech into the core protocol before going public? grtz |
|
|
|
|
|
Mountaingoat
|
|
October 03, 2014, 03:49:59 PM |
|
Ok, there will be limitations in my block explorer. Just finished a dynamic caching module in the back-end because some transactions where just to much for a browser to handle. eg: if one or more outputs are not spend i let the browser render the graph, if all outputs are spend the svg is served without the need for any end-user processing. Simply because unspend outputs can change the graph & i needed some simple & quick caching able to run in the cloud. But visualizing seemingly simple things can give crazy results, check this out: Thats a 6x times zoom in [snip] ( https://chainz.cryptoid.info/xc/tx.dws?f14319b3154e5f6f1c0c46af46159d46308abb47b4e86710af23d8885e81d964.htm) Just someone scraping together about 300 seperate inputs into a single tx-out without time-frame, this has nothing to do with anon (no multisigs) Funny to see how (only for XC) regulair Anon transactions are more easy to handle by a browser (visual tech wise) and how some people had concerns about bloat because of the XCoinshuffle thats part of the anon:D Overall ... am almost there ... Where do you get that stuff from? People say it looks awesome, but I honestly can't figure out why or even how to read it. Do you need to download a program for it? |
|
|
|
|
|
sugarboy321
|
|
October 03, 2014, 03:51:57 PM |
|
Dan that is a Rev 3 feature in the road map sneaky you! The requests for group chat drove this feature to the top of the list!!!! On a side note, I've been contacted by several dev's on a various list of projects - just wanted to keep the community in the loop * Ruble Code review * Britcoin - license rev1 mixer code * Utility Coin - collaboration * Supernet - collaboration Dan "Britcoin license Rev 1 mixer code" XC will license out it's mixer coding? |
|
|
|
|
|
Longenecker
|
|
October 03, 2014, 03:55:15 PM |
|
Why are we collaborating with a coin that is 1 week old (utilitycoin)?
That sounds unwise to me... chances are they are a P&D coin just using collaboration with XC to help push that initial pump...
XC should really only be collaborating with coins that are established and well past that initial P&D phase...
|
|
|
|
|
|
atcsecure
|
|
October 03, 2014, 03:55:38 PM |
|
Dan, After the last time i asked did some research and now understand the need for re-entering the public key for Xchat. But at the same time i feel this will limit the adaptation of XChat by non tech/altcoin people, just because its just a lot of hassle & they have no idea what a private key is. For many i know a XC address looks crazy enough. Is there some (anon related) reason for not letting the wallet discover the public key by itself before encrypting the channel or do you think there is some way to build this tech into the core protocol before going public? grtz I have a different solution for this, using a basic blockchain 2.0 service, the user can register a nickname/alias assigned to the public/private key pair which eliminates that process altogether. Thus you just add the "nickname/alias" Dan |
Join the revolution - XC - Decentralized Trustless Multi-Node Private Transactions
|
|
|
|
atcsecure
|
|
October 03, 2014, 03:57:21 PM |
|
Why are we collaborating with a coin that is 1 week old (utilitycoin)?
That sounds unwise to me... chances are they are a P&D coin just using collaboration with XC to help push that initial pump...
I am in the information gathering stage currently and collecting information Dan |
Join the revolution - XC - Decentralized Trustless Multi-Node Private Transactions
|
|
|
|
Longenecker
|
|
October 03, 2014, 03:59:35 PM |
|
Why are we collaborating with a coin that is 1 week old (utilitycoin)?
That sounds unwise to me... chances are they are a P&D coin just using collaboration with XC to help push that initial pump...
I am in the information gathering stage currently and collecting information Dan Ya but they can sell you anything with sweet talk. Test of time should be requirement... wait for a coin to be established and past it's initial P&D phase. Especially with projects that have anonymous dev's like utility... its very unwise to collaborate with them IMO. |
|
|
|
|
|
Conurtrol
|
|
October 03, 2014, 04:00:07 PM |
|
In the reddit thread there was someone from bitcloud who was very interested in the XC tech. Has he been in touch yet?
|
|
|
|
|
|
Longenecker
|
|
October 03, 2014, 04:03:01 PM |
|
XC should really only be associating itself with coins that are established and have non-anonymous dev's (w/o new bct accounts). There needs to be some sort of strict filtering process... come on now. Just because a coin team asks does not mean XC should agree.
And I see that you wrote on utility's thread basically asking "if the dev's are serious." Really? This stuff should be done through PM. What do you think the bagholders are going to tell you? And if this is the stage that you are at, you should not be telling us that you are collaborating, or even potentially collaborating with them.
|
|
|
|
|
|
laredo7mm
|
|
October 03, 2014, 04:06:41 PM |
|
XC should really only be associating itself with coins that are established and have non-anonymous dev's (w/o new bct accounts). There needs to be some sort of strict filtering process... come on now. Just because a coin team asks does not mean XC should agree.
Before your post, Dan said:
I am in the information gathering stage currently and collecting information
Dan
What part of that don't you understand? It doesn't sound like he has agreed to do anything yet, but he has been contacted. |
|
|
|
|
|
KimmyF
|
|
October 03, 2014, 04:09:50 PM |
|
Dan, After the last time i asked did some research and now understand the need for re-entering the public key for Xchat. But at the same time i feel this will limit the adaptation of XChat by non tech/altcoin people, just because its just a lot of hassle & they have no idea what a private key is. For many i know a XC address looks crazy enough. Is there some (anon related) reason for not letting the wallet discover the public key by itself before encrypting the channel or do you think there is some way to build this tech into the core protocol before going public? grtz I have a different solution for this, using a basic blockchain 2.0 service, the user can register a nickname/alias assigned to the public/private key pair which eliminates that process altogether. Thus you just add the "nickname/alias" Dan you just made my day  |
|
|
|
|
|
laredo7mm
|
|
October 03, 2014, 04:09:55 PM |
|
...And I see that you wrote on utility's thread basically asking "if the dev's are serious." Really? This stuff should be done through PM. What do you think the bagholders are going to tell you? And if this is the stage that you are at, you should not be telling us that you are collaborating, or even potentially collaborating with them.
And if he doesn't let the community know what is going on he gets blasted for not communicating well enough. There is no way to please everyone....obviously. |
|
|
|
|
|
