Show Posts
4141
TestNet Discussion Archive / Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« on: October 27, 2017, 01:13:28 PM »
Alright all, I know a while has passed since we did heavy duty testing. Ive been adding code in to the core for "Temples" and for F8000.
The code is now running on my LAN, but I need to do a little more testing before I release it here to testnet.
It looks like this is going to be Critical to test, as we have to ensure the Temple will not bring down the sanctuaries and its payments are approved by everyone and works smoothly.
I would also like to see f8000 get a good round of testing so we know it will solve our "node mutex" issue in prod, on the very first try. Its critical that once we deem it to be releaseable, that when its released during Christmas and sent as a mandatory that we dont hose up CCEX. So please be watching for f8000 and jump on with an extra server and lets try to verify the hash speed cannot be manipulated by linux vs windows, or multiple linux vs linux.
The retirement accounts are almost ready also, but Im going to deprirotize them right now so I can test my Temple, and Ill explain those later. What to be expected: In the next release, you will start accruing retirement coins. We will at least be able to own some and see the balance. Then in a couple weeks we can test trading them. The trading engine "works" but it needs some business logic to keep it "safe". Its currently getting a harness put in it that allows the escrow trade of colored coins for non-colored asset, with the ability to roll back the trade. This is done by using a complex transaction. The complex transaction piggybacks the output of the first two legs into a new tx and then piggybacks the colored coins on that, along with non colored coins relying on that, so no one can get burned.
Finally this is what I envision a Temple to be:
In TestNet, a temple requires 15MM BBP collateral. It has to run on windows. For now, the only requirement is that it runs on a public IP with IIS, and this user syncs the github pool code in. Im going to be setting one up in an hour so we can test the ecosystem. This will require everyone to upgrade.
Im thinking by the time Christmas hits, we might have ebay integration. The ebay integration requires the Temple owner to apply for an Ebay developer license. Im thinking this Ebay ID might be the "key" that unlocks the payment for the temple. Anyway- the idea here is when a normal wallet user tries to buy a KJV bible, the order will be routed to a temple with a valid Ebay ID and auto-dropped ship to the users house directly from the wallet. This means the temple will BUY the bible and Receive the Escrow. Im going to make it so the temple can charge an extra padding fee to sell the coins if they start losing money on the deal. This is what I think the Temple will provide for the network: A gateway for purchasing valuable products with BBP. (If you are asking why Amazon and Walmart didnt work, they have the API blocked off so that users cant use it for purchases or checkouts. This is deliberate to protect their large billion $ revenue web presence). It makes it impossible to check out an item with AWS or Walmart without clicking the Checkout button on the ecommerce branded site. This however, will hopefully work in-wallet if we can integrate with ebay. Im in talks right now with Zinc, but they seem to be very greedy and high priced, so Ebay is our best bet.
The code is now running on my LAN, but I need to do a little more testing before I release it here to testnet.
It looks like this is going to be Critical to test, as we have to ensure the Temple will not bring down the sanctuaries and its payments are approved by everyone and works smoothly.
I would also like to see f8000 get a good round of testing so we know it will solve our "node mutex" issue in prod, on the very first try. Its critical that once we deem it to be releaseable, that when its released during Christmas and sent as a mandatory that we dont hose up CCEX. So please be watching for f8000 and jump on with an extra server and lets try to verify the hash speed cannot be manipulated by linux vs windows, or multiple linux vs linux.
The retirement accounts are almost ready also, but Im going to deprirotize them right now so I can test my Temple, and Ill explain those later. What to be expected: In the next release, you will start accruing retirement coins. We will at least be able to own some and see the balance. Then in a couple weeks we can test trading them. The trading engine "works" but it needs some business logic to keep it "safe". Its currently getting a harness put in it that allows the escrow trade of colored coins for non-colored asset, with the ability to roll back the trade. This is done by using a complex transaction. The complex transaction piggybacks the output of the first two legs into a new tx and then piggybacks the colored coins on that, along with non colored coins relying on that, so no one can get burned.
Finally this is what I envision a Temple to be:
In TestNet, a temple requires 15MM BBP collateral. It has to run on windows. For now, the only requirement is that it runs on a public IP with IIS, and this user syncs the github pool code in. Im going to be setting one up in an hour so we can test the ecosystem. This will require everyone to upgrade.
Im thinking by the time Christmas hits, we might have ebay integration. The ebay integration requires the Temple owner to apply for an Ebay developer license. Im thinking this Ebay ID might be the "key" that unlocks the payment for the temple. Anyway- the idea here is when a normal wallet user tries to buy a KJV bible, the order will be routed to a temple with a valid Ebay ID and auto-dropped ship to the users house directly from the wallet. This means the temple will BUY the bible and Receive the Escrow. Im going to make it so the temple can charge an extra padding fee to sell the coins if they start losing money on the deal. This is what I think the Temple will provide for the network: A gateway for purchasing valuable products with BBP. (If you are asking why Amazon and Walmart didnt work, they have the API blocked off so that users cant use it for purchases or checkouts. This is deliberate to protect their large billion $ revenue web presence). It makes it impossible to check out an item with AWS or Walmart without clicking the Checkout button on the ecommerce branded site. This however, will hopefully work in-wallet if we can integrate with ebay. Im in talks right now with Zinc, but they seem to be very greedy and high priced, so Ebay is our best bet.
i must go telnet3 folder in main folder ... no setup main masternode but masternode in telnet3 folder 
