I am designing a P2P cryptocurrency exchange that can plug into sites like mtgox and btce: https://bitcointalk.org/index.php?topic=209269.0USSC Litecoin-P2P-Server - A Decentralized P2P Client-Server Application & Exchange For Fast Transactions That Utilize Any Cryptocurrency
Application Features:
1. Directly and internally handles wallet.dat files and the Bitcoin/Litecoin protocol.
2. Completely separate database for user accounts with decentralized replication of virtual-server to other P2P servers.
3. Utilizes banks of wallet.dat files that are not mapped to any specific user account. Evenly distributes coins to internal banks of wallet.dat files.
4. End-user client software accounts are assigned to specific virtual-server allowing transactions speeds comparable to a centralized system like Visa, MasterCard, and Pay-Pal.
5. End-user accounts and wallet.dat banks are replicated to other P2P servers.
6. P2P server network monitors each other for online or offline status. Virtualization server replication to replicate virtual servers across network in the event of physical server seizure or DDOS attack [virtual servers house wallet.dat banks].
7. Double spend attacks are mitigated by denying end-users access to wallet.dat files or banks. [Wallet.dat files are internally encrypted].
8. Uses Bitcoin/Litecoin protocol as a lower level protocol like web-browser applications use the transport layer in the OSI model stack.
9. Uses Bitcoin/Litecoin client and wallet.dat files as lower level application.
10. Eliminates need for confirmations by end-user clients and web-server or web based services.
11. No need for end-user to keep wallet.dat files on local computer or phone. Account is in the P2P cloud.
12. Account cannot be frozen or seized by anyone - even the server operator.
13. No changes to the existing Bitcoin/Litecoin network or protocol. Utilizes existing Litecoin network and protocol.
14. End-user application plug-in to existing Bitcoin/Litecoin client.
15. Government cannot track nor trace nor freeze your funds.
16. Funds cannot be traced.
17. Anyone can run a Bitcoin/Litecoin P2P Server (it's decentralized). If the server goes offline or is seized, the virtual server, accounts, and wallet.dat files are still safe and reallocated to other P2P servers.
19. Can be used as an peer-to-peer (P2P) exchange. Can utilize other exchange sites such as btc-e and mtgox for fiat conversions.
20. Completely Open Source.
This is how to best use cryptocurrency protocols
Bitcoin and other altcoins are best suited to operate as lower level applications and should not be designed for direct end-user control or use. Like web browsers use tcp/ip for lower level operations, the Bitcoin application and protocol should operate much the same way. End-user applications and services need to be built on top of the Bitcoin protocol and application.
There is no need to write code from scratch. all of the above can do coded by combining the bittorrent protocol [for virtual server and wallet.dat bank replication] and onion router protocols [for P2P Server communication] with the existing Bitcoin/Litecoin protocol [This would make a hybrid bittorrent/onion router/Litecoin application].
I will post on here design specs but I will not code it for you.
You have my permission to use the above designs. I will not make a patent or copyright claim against you so long as you keep it open source. I do not own any patents on the above system. It came from meditation and thought.
You don't necessarily have to use the Litecoin protocol, Bitcoin or Worldcoin will work as well. But I recommend the Litecoin Protocol [fast and secure].
I have been an Active Directory admin, and MS Exchange admin, Banyan Vines Street Talk Admin, And have supported everything from X.25 to X.400 and Protocols from RIP, OSFP, BGP, etc...
If you have any questions on how to design the application, I will post answers on here. You can PM me or just post your design questions here. I will help you. If you code an application for this then please give me credit for some of the design. That is all that I ask and maybe a little donations in Litecoin [PM me for address].
Get to Coding.
Thank you.
USSCFounder
Here are some of the first design specs to help you code the above system.
The system should be coded to run on an LAMP server using PHP and MySQL only. Perl can be used to facilitate server side scripts and systems commands as well. The end user client or plug in can be coded in C if desired.
Virtual Servers
Virtual servers are just database tables that give a type of centralization to P2P servers facilitating a single point of transaction for a specific user account; thus allowing for speedy transactions that could not be otherwise obtained by conventional P2P cryptocurrency networks. Virtual servers can be configured to be reassigned to other physical servers in a few minutes in the case of ddos attacks or physical server seizure by authorities.
virtual-server-001.user.table
user-id-key | coins.litecoin | coins.bitcoin | coins.namecoin
(bob) XXXuser-id-key-001XXX | 100 | 0 | 20
(alice) XXXuser-id-key-002XXX | 0 | 100 | 20
The coins can then be evenly distributed so that no one account can be linked to any specific wallet:
virtual-server-001.litecoin.wallet-bank-001.table
wallet-id | coin-amount
wallet.vs-001.bank-001.litecoin-01.dat | 25
wallet.vs-001.bank-001.litecoin-02.dat | 25
wallet.vs-001.bank-001.litecoin-03.dat | 25
wallet.vs-001.bank-001.litecoin-04.dat | 25
virtual-server-001.bitcoin.wallet-bank-001.table
wallet-id | coin-amount
wallet.vs-001.bank-001.bitcoin-01.dat | 25
wallet.vs-001.bank-001.bitcoin-02.dat | 25
wallet.vs-001.bank-001.bitcoin-03.dat | 25
wallet.vs-001.bank-001.bitcoin-04.dat | 25
virtual-server-001.namecoin.wallet-bank-001.table
wallet-id | coin-amount
wallet.vs-001.bank-001.namecoin-01.dat | 10
wallet.vs-001.bank-001.namecoin-02.dat | 10
wallet.vs-001.bank-001.namecoin-03.dat | 10
wallet.vs-001.bank-001.namecoin-04.dat | 10
(MORE TO COME)
Additional design specs:
virtual-server files can then be propagated to other P2P servers simply by sharing the files via bittorent to the other P2P servers:
virtual-server-001 files to be propagated to P2P network:
virtual-server-001.user.table
virtual-server-001.litecoin.wallet-bank-001.table
virtual-server-001.bitcoin.wallet-bank-001.table
virtual-server-001.namecoin.wallet-bank-001.table
wallet.vs-001.bank-001.litecoin-01.dat
wallet.vs-001.bank-001.litecoin-02.dat
wallet.vs-001.bank-001.litecoin-03.dat
wallet.vs-001.bank-001.litecoin-04.dat
wallet.vs-001.bank-001.bitcoin-01.dat
wallet.vs-001.bank-001.bitcoin-02.dat
wallet.vs-001.bank-001.bitcoin-03.dat
wallet.vs-001.bank-001.bitcoin-04.dat
wallet.vs-001.bank-001.namecoin-01.dat
wallet.vs-001.bank-001.namecoin-02.dat
wallet.vs-001.bank-001.namecoin-03.dat
wallet.vs-001.bank-001.namecoin-04.dat
It is that simple to make a virtual-server. Each P2P server would have local copies of the virtual-servers on the network but only a few would actually be online. Every virtual-server would exist in an online state only on one of the P2P servers on the network. That means if virtual-server-001 was online in a New York P2P server, an exact copy of it on the Moscow server would be offline. In the event that the New York server was seized or ddos'ed and went offline, virtual-server-001 would then come online in Moscow.
Its a layered P2P application; one P2P application layered on top of another P2P application.
(MORE TO COME)
|
|
|
|
I am designing a P2P cryptocurrency exchange that can plug into sites like mtgox and btce: https://bitcointalk.org/index.php?topic=209269.0USSC Litecoin-P2P-Server - A Decentralized P2P Client-Server Application & Exchange For Fast Transactions That Utilize Any Cryptocurrency
Application Features:
1. Directly and internally handles wallet.dat files and the Bitcoin/Litecoin protocol.
2. Completely separate database for user accounts with decentralized replication of virtual-server to other P2P servers.
3. Utilizes banks of wallet.dat files that are not mapped to any specific user account. Evenly distributes coins to internal banks of wallet.dat files.
4. End-user client software accounts are assigned to specific virtual-server allowing transactions speeds comparable to a centralized system like Visa, MasterCard, and Pay-Pal.
5. End-user accounts and wallet.dat banks are replicated to other P2P servers.
6. P2P server network monitors each other for online or offline status. Virtualization server replication to replicate virtual servers across network in the event of physical server seizure or DDOS attack [virtual servers house wallet.dat banks].
7. Double spend attacks are mitigated by denying end-users access to wallet.dat files or banks. [Wallet.dat files are internally encrypted].
8. Uses Bitcoin/Litecoin protocol as a lower level protocol like web-browser applications use the transport layer in the OSI model stack.
9. Uses Bitcoin/Litecoin client and wallet.dat files as lower level application.
10. Eliminates need for confirmations by end-user clients and web-server or web based services.
11. No need for end-user to keep wallet.dat files on local computer or phone. Account is in the P2P cloud.
12. Account cannot be frozen or seized by anyone - even the server operator.
13. No changes to the existing Bitcoin/Litecoin network or protocol. Utilizes existing Litecoin network and protocol.
14. End-user application plug-in to existing Bitcoin/Litecoin client.
15. Government cannot track nor trace nor freeze your funds.
16. Funds cannot be traced.
17. Anyone can run a Bitcoin/Litecoin P2P Server (it's decentralized). If the server goes offline or is seized, the virtual server, accounts, and wallet.dat files are still safe and reallocated to other P2P servers.
19. Can be used as an peer-to-peer (P2P) exchange. Can utilize other exchange sites such as btc-e and mtgox for fiat conversions.
20. Completely Open Source.
This is how to best use cryptocurrency protocols
Bitcoin and other altcoins are best suited to operate as lower level applications and should not be designed for direct end-user control or use. Like web browsers use tcp/ip for lower level operations, the Bitcoin application and protocol should operate much the same way. End-user applications and services need to be built on top of the Bitcoin protocol and application.
There is no need to write code from scratch. all of the above can do coded by combining the bittorrent protocol [for virtual server and wallet.dat bank replication] and onion router protocols [for P2P Server communication] with the existing Bitcoin/Litecoin protocol [This would make a hybrid bittorrent/onion router/Litecoin application].
I will post on here design specs but I will not code it for you.
You have my permission to use the above designs. I will not make a patent or copyright claim against you so long as you keep it open source. I do not own any patents on the above system. It came from meditation and thought.
You don't necessarily have to use the Litecoin protocol, Bitcoin or Worldcoin will work as well. But I recommend the Litecoin Protocol [fast and secure].
I have been an Active Directory admin, and MS Exchange admin, Banyan Vines Street Talk Admin, And have supported everything from X.25 to X.400 and Protocols from RIP, OSFP, BGP, etc...
If you have any questions on how to design the application, I will post answers on here. You can PM me or just post your design questions here. I will help you. If you code an application for this then please give me credit for some of the design. That is all that I ask and maybe a little donations in Litecoin [PM me for address].
Get to Coding.
Thank you.
USSCFounder
Here are some of the first design specs to help you code the above system.
The system should be coded to run on an LAMP server using PHP and MySQL only. Perl can be used to facilitate server side scripts and systems commands as well. The end user client or plug in can be coded in C if desired.
Virtual Servers
Virtual servers are just database tables that give a type of centralization to P2P servers facilitating a single point of transaction for a specific user account; thus allowing for speedy transactions that could not be otherwise obtained by conventional P2P cryptocurrency networks. Virtual servers can be configured to be reassigned to other physical servers in a few minutes in the case of ddos attacks or physical server seizure by authorities.
virtual-server-001.user.table
user-id-key | coins.litecoin | coins.bitcoin | coins.namecoin
(bob) XXXuser-id-key-001XXX | 100 | 0 | 20
(alice) XXXuser-id-key-002XXX | 0 | 100 | 20
The coins can then be evenly distributed so that no one account can be linked to any specific wallet:
virtual-server-001.litecoin.wallet-bank-001.table
wallet-id | coin-amount
wallet.vs-001.bank-001.litecoin-01.dat | 25
wallet.vs-001.bank-001.litecoin-02.dat | 25
wallet.vs-001.bank-001.litecoin-03.dat | 25
wallet.vs-001.bank-001.litecoin-04.dat | 25
virtual-server-001.bitcoin.wallet-bank-001.table
wallet-id | coin-amount
wallet.vs-001.bank-001.bitcoin-01.dat | 25
wallet.vs-001.bank-001.bitcoin-02.dat | 25
wallet.vs-001.bank-001.bitcoin-03.dat | 25
wallet.vs-001.bank-001.bitcoin-04.dat | 25
virtual-server-001.namecoin.wallet-bank-001.table
wallet-id | coin-amount
wallet.vs-001.bank-001.namecoin-01.dat | 10
wallet.vs-001.bank-001.namecoin-02.dat | 10
wallet.vs-001.bank-001.namecoin-03.dat | 10
wallet.vs-001.bank-001.namecoin-04.dat | 10
(MORE TO COME)
Additional design specs:
virtual-server files can then be propagated to other P2P servers simply by sharing the files via bittorent to the other P2P servers:
virtual-server-001 files to be propagated to P2P network:
virtual-server-001.user.table
virtual-server-001.litecoin.wallet-bank-001.table
virtual-server-001.bitcoin.wallet-bank-001.table
virtual-server-001.namecoin.wallet-bank-001.table
wallet.vs-001.bank-001.litecoin-01.dat
wallet.vs-001.bank-001.litecoin-02.dat
wallet.vs-001.bank-001.litecoin-03.dat
wallet.vs-001.bank-001.litecoin-04.dat
wallet.vs-001.bank-001.bitcoin-01.dat
wallet.vs-001.bank-001.bitcoin-02.dat
wallet.vs-001.bank-001.bitcoin-03.dat
wallet.vs-001.bank-001.bitcoin-04.dat
wallet.vs-001.bank-001.namecoin-01.dat
wallet.vs-001.bank-001.namecoin-02.dat
wallet.vs-001.bank-001.namecoin-03.dat
wallet.vs-001.bank-001.namecoin-04.dat
It is that simple to make a virtual-server. Each P2P server would have local copies of the virtual-servers on the network but only a few would actually be online. Every virtual-server would exist in an online state only on one of the P2P servers on the network. That means if virtual-server-001 was online in a New York P2P server, an exact copy of it on the Moscow server would be offline. In the event that the New York server was seized or ddos'ed and went offline, virtual-server-001 would then come online in Moscow.
Its a layered P2P application; one P2P application layered on top of another P2P application.
(MORE TO COME)
|
|
|
|
|
Additional design specs:
virtual-server files can then be propagated to other P2P servers simply by sharing the files via bittorent to the other P2P servers:
virtual-server-001 files to be propagated to P2P network:
virtual-server-001.user.table
virtual-server-001.litecoin.wallet-bank-001.table
virtual-server-001.bitcoin.wallet-bank-001.table
virtual-server-001.namecoin.wallet-bank-001.table
wallet.vs-001.bank-001.litecoin-01.dat
wallet.vs-001.bank-001.litecoin-02.dat
wallet.vs-001.bank-001.litecoin-03.dat
wallet.vs-001.bank-001.litecoin-04.dat
wallet.vs-001.bank-001.bitcoin-01.dat
wallet.vs-001.bank-001.bitcoin-02.dat
wallet.vs-001.bank-001.bitcoin-03.dat
wallet.vs-001.bank-001.bitcoin-04.dat
wallet.vs-001.bank-001.namecoin-01.dat
wallet.vs-001.bank-001.namecoin-02.dat
wallet.vs-001.bank-001.namecoin-03.dat
wallet.vs-001.bank-001.namecoin-04.dat
It is that simple to make a virtual-server. Each P2P server would have local copies of the virtual-servers on the network but only a few would actually be online. Every virtual-server would exist in an online state only on one on three or more of the P2P servers on the network. That means if virtual-server-001 was online in a New York P2P server, an exact copy of it on the Moscow server would be offline. In the event that the New York server was seized or ddos'ed and went offline, virtual-server-001 would then come online in Moscow.
Its a layered P2P application; one P2P application layered on top of another P2P application.
(MORE TO COME)
|
|
|
|
I am designing a P2P cryptocurrency exchange that can plug into sites like mtgox and btce: https://bitcointalk.org/index.php?topic=209269.0USSC Litecoin-P2P-Server - A Decentralized P2P Client-Server Application & Exchange For Fast Transactions That Utilize Any Cryptocurrency
Application Features:
1. Directly and internally handles wallet.dat files and the Bitcoin/Litecoin protocol.
2. Completely separate database for user accounts with decentralized replication of virtual-server to other P2P servers.
3. Utilizes banks of wallet.dat files that are not mapped to any specific user account. Evenly distributes coins to internal banks of wallet.dat files.
4. End-user client software accounts are assigned to specific virtual-server allowing transactions speeds comparable to a centralized system like Visa, MasterCard, and Pay-Pal.
5. End-user accounts and wallet.dat banks are replicated to other P2P servers.
6. P2P server network monitors each other for online or offline status. Virtualization server replication to replicate virtual servers across network in the event of physical server seizure or DDOS attack [virtual servers house wallet.dat banks].
7. Double spend attacks are mitigated by denying end-users access to wallet.dat files or banks. [Wallet.dat files are internally encrypted].
8. Uses Bitcoin/Litecoin protocol as a lower level protocol like web-browser applications use the transport layer in the OSI model stack.
9. Uses Bitcoin/Litecoin client and wallet.dat files as lower level application.
10. Eliminates need for confirmations by end-user clients and web-server or web based services.
11. No need for end-user to keep wallet.dat files on local computer or phone. Account is in the P2P cloud.
12. Account cannot be frozen or seized by anyone - even the server operator.
13. No changes to the existing Bitcoin/Litecoin network or protocol. Utilizes existing Litecoin network and protocol.
14. End-user application plug-in to existing Bitcoin/Litecoin client.
15. Government cannot track nor trace nor freeze your funds.
16. Funds cannot be traced.
17. Anyone can run a Bitcoin/Litecoin P2P Server (it's decentralized). If the server goes offline or is seized, the virtual server, accounts, and wallet.dat files are still safe and reallocated to other P2P servers.
19. Can be used as an peer-to-peer (P2P) exchange. Can utilize other exchange sites such as btc-e and mtgox for fiat conversions.
20. Completely Open Source.
This is how to best use cryptocurrency protocols
Bitcoin and other altcoins are best suited to operate as lower level applications and should not be designed for direct end-user control or use. Like web browsers use tcp/ip for lower level operations, the Bitcoin application and protocol should operate much the same way. End-user applications and services need to be built on top of the Bitcoin protocol and application.
There is no need to write code from scratch. all of the above can do coded by combining the bittorrent protocol [for virtual server and wallet.dat bank replication] and onion router protocols [for P2P Server communication] with the existing Bitcoin/Litecoin protocol [This would make a hybrid bittorrent/onion router/Litecoin application].
I will post on here design specs but I will not code it for you.
You have my permission to use the above designs. I will not make a patent or copyright claim against you so long as you keep it open source. I do not own any patents on the above system. It came from meditation and thought.
You don't necessarily have to use the Litecoin protocol, Bitcoin or Worldcoin will work as well. But I recommend the Litecoin Protocol [fast and secure].
I have been an Active Directory admin, and MS Exchange admin, Banyan Vines Street Talk Admin, And have supported everything from X.25 to X.400 and Protocols from RIP, OSFP, BGP, etc...
If you have any questions on how to design the application, I will post answers on here. You can PM me or just post your design questions here. I will help you. If you code an application for this then please give me credit for some of the design. That is all that I ask and maybe a little donations in Litecoin [PM me for address].
Get to Coding.
Thank you.
USSCFounder
Here are some of the first design specs to help you code the above system.
The system should be coded to run on an LAMP server using PHP and MySQL only. Perl can be used to facilitate server side scripts and systems commands as well. The end user client or plug in can be coded in C if desired.
Virtual Servers
Virtual servers are just database tables that give a type of centralization to P2P servers facilitating a single point of transaction for a specific user account; thus allowing for speedy transactions that could not be otherwise obtained by conventional P2P cryptocurrency networks. Virtual servers can be configured to be reassigned to other physical servers in a few minutes in the case of ddos attacks or physical server seizure by authorities.
virtual-server-001.user.table
user-id-key | coins.litecoin | coins.bitcoin | coins.namecoin
(bob) XXXuser-id-key-001XXX | 100 | 0 | 20
(alice) XXXuser-id-key-002XXX | 0 | 100 | 20
The coins can then be evenly distributed so that no one account can be linked to any specific wallet:
virtual-server-001.litecoin.wallet-bank-001.table
wallet-id | coin-amount
wallet.vs-001.bank-001.litecoin-01.dat | 25
wallet.vs-001.bank-001.litecoin-02.dat | 25
wallet.vs-001.bank-001.litecoin-03.dat | 25
wallet.vs-001.bank-001.litecoin-04.dat | 25
virtual-server-001.bitcoin.wallet-bank-001.table
wallet-id | coin-amount
wallet.vs-001.bank-001.bitcoin-01.dat | 25
wallet.vs-001.bank-001.bitcoin-02.dat | 25
wallet.vs-001.bank-001.bitcoin-03.dat | 25
wallet.vs-001.bank-001.bitcoin-04.dat | 25
virtual-server-001.namecoin.wallet-bank-001.table
wallet-id | coin-amount
wallet.vs-001.bank-001.namecoin-01.dat | 10
wallet.vs-001.bank-001.namecoin-02.dat | 10
wallet.vs-001.bank-001.namecoin-03.dat | 10
wallet.vs-001.bank-001.namecoin-04.dat | 10
(MORE TO COME)
Additional design specs:
virtual-server files can then be propagated to other P2P servers simply by sharing the files via bittorent to the other P2P servers:
virtual-server-001 files to be propagated to P2P network:
virtual-server-001.user.table
virtual-server-001.litecoin.wallet-bank-001.table
virtual-server-001.bitcoin.wallet-bank-001.table
virtual-server-001.namecoin.wallet-bank-001.table
wallet.vs-001.bank-001.litecoin-01.dat
wallet.vs-001.bank-001.litecoin-02.dat
wallet.vs-001.bank-001.litecoin-03.dat
wallet.vs-001.bank-001.litecoin-04.dat
wallet.vs-001.bank-001.bitcoin-01.dat
wallet.vs-001.bank-001.bitcoin-02.dat
wallet.vs-001.bank-001.bitcoin-03.dat
wallet.vs-001.bank-001.bitcoin-04.dat
wallet.vs-001.bank-001.namecoin-01.dat
wallet.vs-001.bank-001.namecoin-02.dat
wallet.vs-001.bank-001.namecoin-03.dat
wallet.vs-001.bank-001.namecoin-04.dat
It is that simple to make a virtual-server. Each P2P server would have local copies of the virtual-servers on the network but only a few would actually be online. Every virtual-server would exist in an online state only on one of the P2P servers on the network. That means if virtual-server-001 was online in a New York P2P server, an exact copy of it on the Moscow server would be offline. In the event that the New York server was seized or ddos'ed and went offline, virtual-server-001 would then come online in Moscow.
Its a layered P2P application; one P2P application layered on top of another P2P application.
(MORE TO COME)
The idea came from trying to stop all of the new alternate cryptocurrencies being released daily: https://bitcointalk.org/index.php?topic=208327.20If you would like to help with this project please PM me. If you have any questions you can post them in the above discussion. |
|
|
|
|
Here are some of the first design specs to help you code the above system.
The system should be coded to run on an LAMP server using PHP and MySQL only. Perl can be used to facilitate server side scripts and systems commands as well. The end user client or plug in can be coded in C if desired.
Virtual Servers
Virtual servers are just database tables that give a type of centralization to P2P servers facilitating a single point of transaction for a specific user account; thus allowing for speedy transactions that could not be otherwise obtained by conventional P2P cryptocurrency networks. Virtual servers can be configured to be reassigned to other physical servers in a few minutes in the case of ddos attacks or physical server seizure by authorities.
virtual-server-001.user.table
user-id-key | coins.litecoin | coins.bitcoin | coins.namecoin
(bob) XXXuser-id-key-001XXX | 100 | 0 | 20
(alice) XXXuser-id-key-002XXX | 0 | 100 | 20
The coins can then be evenly distributed so that no one account can be linked to any specific wallet:
virtual-server-001.litecoin.wallet-bank-001.table
wallet-id | coin-amount
wallet.vs-001.bank-001.litecoin-01.dat | 25
wallet.vs-001.bank-001.litecoin-02.dat | 25
wallet.vs-001.bank-001.litecoin-03.dat | 25
wallet.vs-001.bank-001.litecoin-04.dat | 25
virtual-server-001.bitcoin.wallet-bank-001.table
wallet-id | coin-amount
wallet.vs-001.bank-001.bitcoin-01.dat | 25
wallet.vs-001.bank-001.bitcoin-02.dat | 25
wallet.vs-001.bank-001.bitcoin-03.dat | 25
wallet.vs-001.bank-001.bitcoin-04.dat | 25
virtual-server-001.namecoin.wallet-bank-001.table
wallet-id | coin-amount
wallet.vs-001.bank-001.namecoin-01.dat | 10
wallet.vs-001.bank-001.namecoin-02.dat | 10
wallet.vs-001.bank-001.namecoin-03.dat | 10
wallet.vs-001.bank-001.namecoin-04.dat | 10
(MORE TO COME)
|
|
|
|
|
Bitcoin and other altcoins are best suited to operate as lower level applications and should not be designed for direct end-user control or use. Like web browsers use tcp/ip for lower level operations, the Bitcoin application and protocol should operate much the same way. End-user applications and services need to be built on top of the Bitcoin protocol and application.
I left out:
"Should use client side passphrase and server side passphrase to give access to encrypted user account on virtual server."
The above should stop any server admin/owner from trying to hack any specific users account. Client side passphrase + server side passphrase = access key to access user account on virtual server. Using combined key, client side can access server side Db for that specific user account only. Kind of like how the truecrypt client accesses an encrypted hard drive. Nothing is stored on the users client side. Server side can be configured to use third-party authentication if necessary [i.e other website, yubi-key, etc...]
|
|
|
|
|
I left out
Should use client side passphrase and server side passphrase to give access to encrypted user account on virtual server.
The above should stop any server admin/owner from trying to hack any specific users account. Client side passphrase + server side passphrase = access key to access user account on virtual server. Using combined key, client side can access server side Db for that specific user account only. Kind of like how the truecrypt client accesses an encrypted hard drive. Nothing is stored on the users client side. Server side can be configured to use third-party authentication if necessary [i.e other website, yubi-key, etc...]
|
|
|
|
You cannot use a decentralized currency directly in the way you are suggesting. The number of confirmations and the amount of time they take are what make transactions secure and valid. Decreasing the number of confirmations required and the time per confirmations increases the risk of double spending. I'm not sure you understand this.
I am also sure that in time as more third party services as described become available they would become cheaper. There is nothing to stop larger business also developing there own software which provides this service. Each business would be in competition to provide the simplest and cheapest option.
Maybe you are suggesting that the developers of a new cryptocurrency should include such software as part of the package and at no cost to the user.
I have come up with another solution that will work for sure. Will post in a few minutes. This should kill the debate completely. It solves all of the problems and it uses Bitcoin/Litecoin the way that I believe Satoshi envisioned. Link: https://bitcointalk.org/index.php?topic=209269.0USSC Litecoin-P2P-Server - A Decentralized P2P Client-Server Application For Fast Transactions That Utilize The Litecoin Network
Application Features:
1. Directly and internally handles wallet.dat files and the Litecoin protocol.
2. Completely separate database for user accounts with decentralized replication to other P2P servers.
3. Utilizes banks of wallet.dat files that are not mapped to any specific user account. Evenly distributes coins to internal banks of wallet.dat files.
4. End-user client software accounts are assigned to specific server allowing transactions speeds comparable to a centralized system like Visa, MasterCard, and Pay-Pal.
5. End-user accounts and wallet.dat banks are replicated to other P2P servers.
6. P2P server network monitors each other for online or offline status. Virtualization server replication to replicate virtual servers across network in the event of physical server seizure or DDOS attack [virtual servers house wallet.dat banks].
7. Double spend attacks are mitigated by denying end-users access to wallet.dat files or banks. [Wallet.dat files are internally encrypted].
8. Uses Litecoin protocol as a lower level protocol like web-browser applications use the transport layer in the OSI model stack.
9. Uses Litecoin client and wallet.dat files as lower level application.
10. Eliminates need for confirmations by end-user clients and web-server or web based services.
11. No need for end-user to keep wallet.dat files on local computer or phone. Account is in the P2P cloud.
12. Account cannot be frozen or seized by anyone - even the server operator.
13. No changes to the existing Litecoin network or protocol. Utilizes existing Litecoin network and protocol.
14. End-user application plug-in to existing Litecoin client.
15. Government cannot track nor trace nor freeze your funds.
16. Funds cannot be traced.
17. Anyone can run a Litecoin P2P Server (it's decentralized). If the server goes offline or is seized, the virtual server, accounts, and wallet.dat files are still safe and reallocated to other P2P servers.
19. Completely Open Source.
This is how to best use cryptocurrency protocols
There is no need to write code from scratch. all of the above can do coded by combining the bittorrent protocol [for virtual server and wallet.dat bank replication] and onion router protocols [for P2P Server communication] with the existing Litecoin protocol [This would make a hybrid bittorrent/onion router/Litecoin application].
I will post on here design specs but I will not code it for you.
You have my permission to use the above designs. I will not make a patent or copyright claim against you so long as you keep it open source. I do not own any patents on the above system. It came from meditation and thought.
You don't necessarily have to use the Litecoin protocol, Bitcoin or Worldcoin will work as well. But I recommend the Litecoin Protocol [fast and secure].
I have been an Active Directory admin, and MS Exchange admin, Banyan Vines Street Talk Admin, And have supported everything from X.25 to X.400 and Protocols from RIP, OSFP, BGP, etc...
If you have any questions on how to design the application, I will post answers on here. You can PM me or just post your design questions here. I will help you. If you code an application for this then please give me credit for some of the design. That is all that I ask and maybe a little donations in Litecoin [PM me for address].
Get to Coding.
Thank you.
USSCFounder
Link: https://bitcointalk.org/index.php?topic=209269.0 |
|
|
|
|
USSC Litecoin-P2P-Server - A Decentralized P2P Client-Server Application & Exchange For Fast Transactions That Utilize Any Cryptocurrency
Application Features:
1. Directly and internally handles wallet.dat files and the Bitcoin/Litecoin protocol.
2. Completely separate database for user accounts with decentralized replication of virtual-server to other P2P servers.
3. Utilizes banks of wallet.dat files partial wallet private keys that are not mapped to any specific user account. Evenly distributes coins to internal banks of wallet.dat files partial wallet private keys. (SEE POSTS BELOW IN DISPOSABLE WALLET SECTION)
4. End-user client software accounts are assigned to specific virtual-server allowing transactions speeds comparable to a centralized system like Visa, MasterCard, and Pay-Pal.
5. End-user accounts and wallet.dat banks are replicated to other P2P servers.
6. P2P server network monitors each other for online or offline status. Virtualization server replication to replicate virtual servers across network in the event of physical server seizure or DDOS attack [virtual servers house wallet.dat banks].
7. Double spend attacks are mitigated by denying end-users access to wallet.dat files or banks. [Wallet.dat files are internally encrypted].
8. Uses Bitcoin/Litecoin protocol as a lower level protocol like web-browser applications use the transport layer in the OSI model stack.
9. Uses Bitcoin/Litecoin client and wallet.dat files as lower level application.
10. Eliminates need for confirmations by end-user clients and web-server or web based services.
11. No need for end-user to keep wallet.dat files on local computer or phone. Account is in the P2P cloud.
12. Account cannot be frozen or seized by anyone - even the server operator.
13. No changes to the existing Bitcoin/Litecoin network or protocol. Utilizes existing Litecoin network and protocol.
14. End-user application plug-in to existing Bitcoin/Litecoin client.
15. Government cannot track nor trace nor freeze your funds.
16. Funds cannot be traced.
17. Anyone can run a Bitcoin/Litecoin P2P Server (it's decentralized). If the server goes offline or is seized, the virtual server, accounts, and wallet.dat files are still safe and reallocated to other P2P servers.
19. Can be used as an peer-to-peer (P2P) exchange. Can utilize other exchange sites such as btc-e and mtgox for fiat conversions.
20. Completely Open Source.
This is how to best use cryptocurrency protocols
Bitcoin and other altcoins are best suited to operate as lower level applications and should not be designed for direct end-user control or use. Like web browsers use tcp/ip for lower level operations, the Bitcoin application and protocol should operate much the same way. End-user applications and services need to be built on top of the Bitcoin protocol and application.
There is no need to write code from scratch. all of the above can do coded by combining the bittorrent protocol [for virtual server and wallet.dat bank replication] and onion router protocols [for P2P Server communication] with the existing Bitcoin/Litecoin protocol [This would make a hybrid bittorrent/onion router/Litecoin application].
I will post on here design specs but I will not code it for you.
You have my permission to use the above designs. I will not make a patent or copyright claim against you so long as you keep it open source. I do not own any patents on the above system. It came from meditation and thought.
You don't necessarily have to use the Litecoin protocol, Bitcoin or Worldcoin will work as well. But I recommend the Litecoin Protocol [fast and secure].
I have been an Active Directory admin, and MS Exchange admin, Banyan Vines Street Talk Admin, And have supported everything from X.25 to X.400 and Protocols from RIP, OSFP, BGP, etc...
If you have any questions on how to design the application, I will post answers on here. You can PM me or just post your design questions here. I will help you. If you code an application for this then please give me credit for some of the design. That is all that I ask and maybe a little donations in Litecoin [PM me for address].
Get to Coding.
Thank you.
USSCFounder
|
|
|
|
You cannot use a decentralized currency directly in the way you are suggesting. The number of confirmations and the amount of time they take are what make transactions secure and valid. Decreasing the number of confirmations required and the time per confirmations increases the risk of double spending. I'm not sure you understand this.
I am also sure that in time as more third party services as described become available they would become cheaper. There is nothing to stop larger business also developing there own software which provides this service. Each business would be in competition to provide the simplest and cheapest option.
Maybe you are suggesting that the developers of a new cryptocurrency should include such software as part of the package and at no cost to the user.
I have come up with another solution that will work for sure. Will post in a few minutes. |
|
|
|
|
The above solution could also be used like a giftcard. Simply by using the merchants public key you can load coins to be used at that merchant or group of merchants using parent and sub-keys.
A merchant would not have to do confirmations at all because they could look directly into their key-wallet and see the funds are already there before you even arrive at the location. They would not be able to spend the funds without your pass-code.
1. Bob sends Alice 100 coins using Alice's public key. Altcoin client removes 100 coins from Bob's wallet. Altcoin client sets 24 hour time limit on transaction. Passcode must be entered into transaction before time limit or funds get returned. Altcoin client sends coins to the Cloud secured by Alice's public key. Bob cannot retrieve funds until after time limit expires.
2. Alice receives coins in key wallet and verifies coins with private key.
3. Alice cannot spend coins without bobs pass-code.
4. Bob meets Alice in person and inspects merchandise.
5. Bob sees merchandise is good and gives Alice pass-code to unlock coins.
6. If merchandise is bad Bob does not give Alice pass-code and the funds are returned to Bob's wallet when the 24 hour time limit expires.
|
|
|
|
You cannot use a decentralized currency directly in the way you are suggesting. The number of confirmations and the amount of time they take are what make transactions secure and valid. Decreasing the number of confirmations required and the time per confirmations increases the risk of double spending. I'm not sure you understand this.
I am also sure that in time as more third party services as described become available they would become cheaper. There is nothing to stop larger business also developing there own software which provides this service. Each business would be in competition to provide simplest and cheapest option.
Maybe you are suggesting that the developers of a new cryptocurrency should include software like this as part of the package and has no cost to the user.
Did you read the link I posted above here? : https://bitcointalk.org/index.php?topic=208327.0How about an p2p escrow ledger with a Point of Sale Passcode.
For example lets say I am on my way to Walmart.
1. I tell my altcoin client to reserve 20 coins for walmarts use with a time limit of 24 hours.
2. I then reserve the amount using walmarts public key to reserve the amount in my wallet.
3. the altcoin network will remove the coins from my wallet and put them in escrow.
4. the coins cannot be sent to anyone or spent by anyone who does not have walmarts private key.
5. I goto walmart and spend 10 coins.
6. Walmart altcoin client sees that there is a reserve amount of 20 coins with walmarts public key signature.
7. Walmart then receives 10 coins from the reserve and using its private key releases the rest of the coins back into my wallet freeing up the remaining 10 coins for me to spend.
This is just an idea on how to speed up transactions.
Let me know what you think.
You can also incorporate a passcode into step 2. that way if Walmart is part of a group of retailers sharing the same private key then I can keep a larger amount in p2p escrow for use with multiple retailers. the only retailers that could take money out would be those that I am present in with my passcode ready. The system could also be used for e-bay and the postal delivery service: 1. a seller on e-bay want to sell you a mining rig for 100 altcoins 1. e-bay seller gives you his public key 2. You reserve into escrow 100 altcoins using the public keys of the e-bay seller, e-bay, and UPS delivery service. The altcoin client removes the 100 altcoins from your wallet and puts them into the cloud secured by the public keys of the e-bay seller, e-bay, and the UPS delivery service. 3. Upon completion of the sale ebay signs the transaction with their private key. 4. Upon delivery and inspection of the mining rig the UPS delivery man signs the transaction with his private key. 5. When all the transaction has been signed by all of the private keys (matching the public keys already incorporated into the transaction) the 100 altcoins are transferred to the e-bay seller. anyone else have input? [UPDATE] I created and announced a project post for this idea here: https://bitcointalk.org/index.php?topic=208393.0Why could not that system work? No one has debunked my solution yet. |
|
|
|
POS for a shop called be solved. Look at the systems used on exchange websites. Instead of transferring your cryptocurrency directly from your personal wallet when buying a product, you place the currency in an on site account. Businesses could use an in store login service. Obviously this only functions if you know you are intending to shop at a particular store. There is nothing to stop business producing these services at zero expense to the customer and there is no need to wait for confirmations.
Unfortunately, most businesses charge for these services. They are not free. Then you would have to have a monopoly type service that all the business agree upon. an altcoin that could be used at a Point of Sale would empower the people and small to midsize businesses. |
|
|
|
if the crypto-community really wants to see crypto take off they are going to have to find a way for point of sale (POS) systems to use the coins. Yes, we know that Point of Sale systems can use a third party for bitcoin transactions
Is it such a big deal? I don't think it's realistic to expect that coins will ever leave the internet. Make online shops accept it first. There is already a trend to merge online and storefront sales. Just look at gyft.com . Cryptocurrency can be used on the internet or off using QR codes. The problem with offline sales is that the confirmation times are too long to make this feasible. |
|
|
|
|
The system could also be used for e-bay and the postal delivery service:
1. a seller on e-bay want to sell you a mining rig for 100 altcoins
1. e-bay seller gives you his public key
2. You reserve into escrow 100 altcoins using the public keys of the e-bay seller, e-bay, and UPS delivery service. The altcoin client removes the 100 altcoins from your wallet and puts them into the cloud secured by the public keys of the e-bay seller, e-bay, and the UPS delivery service.
3. Upon completion of the sale ebay signs the transaction with their private key.
4. Upon delivery and inspection of the mining rig the UPS delivery man signs the transaction with his private key.
5. When all the transaction has been signed by all of the private keys (matching the public keys already incorporated into the transaction) the 100 altcoins are transferred to the e-bay seller.
anyone else have input?
|
|
|
|
This is a project for an alt-coin that I would like to request to be made. I got the idea while replying to a post here: https://bitcointalk.org/index.php?topic=208327.0Here is a Quote from the above post: How about an p2p escrow ledger with a Point of Sale Passcode.
For example lets say I am on my way to Walmart.
1. I tell my altcoin client to reserve 20 coins for walmarts use with a time limit of 24 hours.
2. I then reserve the amount using walmarts public key to reserve the amount in my wallet.
3. the altcoin network will remove the coins from my wallet and put them in escrow.
4. the coins cannot be sent to anyone or spent by anyone who does not have walmarts private key.
5. I goto walmart and spend 10 coins.
6. Walmart altcoin client sees that there is a reserve amount of 20 coins with walmarts public key signature.
7. Walmart then receives 10 coins from the reserve and using its private key releases the rest of the coins back into my wallet freeing up the remaining 10 coins for me to spend.
This is just an idea on how to speed up transactions.
Let me know what you think.
You can also incorporate a passcode into step 2. that way if Walmart is part of a group of retailers sharing the same private key then I can keep a larger amount in p2p escrow for use with multiple retailers. the only retailers that could take money out would be those that I am present in with my passcode ready. The above solution could also be used like a giftcard. Simply by using the merchants public key you can load coins to be used at that merchant or group of merchants using parent and sub-keys. A merchant would not have to do confirmations at all because they could look directly into their key-wallet and see the funds are already there before you even arrive at the location. They would not be able to spend the funds without your pass-code. 1. Bob sends Alice 100 coins using Alice's public key. Altcoin client removes 100 coins from Bob's wallet. Altcoin client sets 24 hour time limit on transaction. Passcode must be entered into transaction before time limit or funds get returned. Altcoin client sends coins to the Cloud secured by Alice's public key. Bob cannot retrieve funds until after time limit expires. 2. Alice receives coins in key wallet and verifies coins with private key. 3. Alice cannot spend coins without bobs pass-code. 4. Bob meets Alice in person and inspects merchandise. 5. Bob sees merchandise is good and gives Alice pass-code to unlock coins. 6. If merchandise is bad Bob does not give Alice pass-code and the funds are returned to Bob's wallet when the 24 hour time limit expires. I believe we can take the Litecoin client and modify it to perform what is stated above. Is there anyone who is willing to get together and colaborate on a coin for fast Point of Sale Transactions? |
|
|
|
How about an p2p escrow ledger with a Point of Sale Passcode.
For example lets say I am on my way to Walmart.
1. I tell my altcoin client to reserve 20 coins for walmarts use with a time limit of 24 hours.
2. I then reserve the amount using walmarts public key to reserve the amount in my wallet.
3. the altcoin network will remove the coins from my wallet and put them in escrow.
4. the coins cannot be sent to anyone or spent by anyone who does not have walmarts private key.
5. I goto walmart and spend 10 coins.
6. Walmart altcoin client sees that there is a reserve amount of 20 coins with walmarts public key signature.
7. Walmart then receives 10 coins from the reserve and using its private key releases the rest of the coins back into my wallet freeing up the remaining 10 coins for me to spend.
This is just an idea on how to speed up transactions.
Let me know what you think.
You can also incorporate a passcode into step 2. that way if Walmart is part of a group of retailers sharing the same private key then I can keep a larger amount in p2p escrow for use with multiple retailers. the only retailers that could take money out would be those that I am present in with my passcode ready. The system could also be used for e-bay and the postal delivery service: 1. a seller on e-bay want to sell you a mining rig for 100 altcoins 1. e-bay seller gives you his public key 2. You reserve into escrow 100 altcoins using the public keys of the e-bay seller, e-bay, and UPS delivery service. The altcoin client removes the 100 altcoins from your wallet and puts them into the cloud secured by the public keys of the e-bay seller, e-bay, and the UPS delivery service. 3. Upon completion of the sale ebay signs the transaction with their private key. 4. Upon delivery and inspection of the mining rig the UPS delivery man signs the transaction with his private key. 5. When all the transaction has been signed by all of the private keys (matching the public keys already incorporated into the transaction) the 100 altcoins are transferred to the e-bay seller. anyone else have input? [UPDATE] I created and announced a project post for this idea here: https://bitcointalk.org/index.php?topic=208393.0 |
|
|
|
|
How about an p2p escrow ledger with a Point of Sale Passcode.
For example lets say I am on my way to Walmart.
1. I tell my altcoin client to reserve 20 coins for walmarts use with a time limit of 24 hours.
2. I then reserve the amount using walmarts public key to reserve the amount in my wallet.
3. the altcoin network will remove the coins from my wallet and put them in escrow.
4. the coins cannot be sent to anyone or spent by anyone who does not have walmarts private key.
5. I goto walmart and spend 10 coins.
6. Walmart altcoin client sees that there is a reserve amount of 20 coins with walmarts public key signature.
7. Walmart then receives 10 coins from the reserve and using its private key releases the rest of the coins back into my wallet freeing up the remaining 10 coins for me to spend.
This is just an idea on how to speed up transactions.
Let me know what you think.
|
|
|
|
|
Show Posts
