There will be a mobile app for iOS and Android, they should be accepted at the app stores of Apple and Google.  From within the mobile app you have full control over the dapp store and can launch your dapps from there. Of course the dapp needs to be responsive for this. - Github (centralized method) - 3rd party decentralized storage (decentralized method); we can't disclose yet who this will be, in the future there will be more than one option When you install a dapp on your node, you will download it. Then all files are on your node. When you use the full client, it will use the local dapp sources. When you use the lite client you won't install it locally, it will connect to one of the (maximum 16 for now) master nodes and use their dapp sources. Every dapp has its own side chain (custom chain). This is our interpretation of a decentralized application. While a smart contract always runs on the main chain, a dapp always has its own side chain. So executable dapp code can run on a maximum of 16 full node servers, who then service X "lite" node runners who "log in" to use the dapp on the master nodes. Are these master nodes all Forging Delegates, all Standby delegates, or can they be a mixture of both? It sounds like the dapp author would want his side chain to be ALL on dedicated Standby Delegate servers and NOT on the Forging Delegate servers, because if ALL side chains are run by the 101 Club, they will get bogged down with running too many chains, right? Does the custom side chain have to be running on the same 16 max master full node servers running the executable dapp code? The 16 master dapp nodes are processing possible changes / additions to the custom side chain and adding new blocks to it every 10 seconds, right? Does this system mean that the owner of a dapp can send out a "contract closure" message to settle open contracts? If so, doesn't this mean a single server from the 101 club will have to settle all open dapp contracts within one blocktime upon receiving a closure trigger message? Isn't this really difficult, since the contracts can be scattered through many GB of the main blockchain? Will there be limits on the total number of open contracts or the time period over which they must be made and settled? |
|
|
|
There will be a mobile app for iOS and Android, they should be accepted at the app stores of Apple and Google. From within the mobile app you have full control over the dapp store and can launch your dapps from there. Of course the dapp needs to be responsive for this. OK, so there's dapps in the Crypti dapp store. What is the plan for where these dapp files are stored? As files on a single Crypti website server? As files on all 101 Delegate servers? As data on seperate custom XCR side chains? In my garage, Mal:  Right there, behind the bullion  I hope you remember to lower your garage door when you drive off to work. Wait a minute, with that much bullion.... |
|
|
|
There will be a mobile app for iOS and Android, they should be accepted at the app stores of Apple and Google. From within the mobile app you have full control over the dapp store and can launch your dapps from there. Of course the dapp needs to be responsive for this. OK, so there's dapps in the Crypti dapp store. What is the plan for where these dapp files are stored? As files on a single Crypti website server? As files on all 101 Delegate servers? As data on seperate custom XCR side chains? |
|
|
|
|
Hey , Max, could you please change the whitepaper link on page 1 of this thread to point at the NEW whitepaper? Thx...
|
|
|
|
Let me start a rambling discussion on the upcoming XCR custom blockchain capabilities.
According to several posters here, the Apple and Android (A&A) app stores are apparently unfriendly to cryptocurrency apps. If so, there needs to be an alternate way to distribute cryptocoin apps outside of the Apple and Android ecosystems. So, is it possible to create an app for both A&A that would take the contents of a new Crypti side chain, validate it as coming from a trusted or previously utilized source, and then load that side chain data as a new or upgraded existing app that would be run on an A or A smartphone?
Basically I am proposing that we at XCR only need to get a single app accepted by A&A, which would be a "plain vanilla" XCR side chain code loader app. This would allow all other apps using XCR to be accessed and downloaded not thru A&A but from new XCR side chains. This vanilla XCR app, once loaded on a smartphone, could then watch for new XCR side chains (and thus new XCR apps) and alert the user when new XCR-specific apps were available. This would allow the (anonymous?) publication of new XCR apps, prevent censorship of apps by A&A, and keep new XCR apps from being lost in the daily noise of all other apps routinely added to the A&A App Stores.
Is this doable? A reasonably good idea?
The good news is that Crypti has web-wallet, thus, browser on iPhone coulde be "the app" itself. User just need to know the mobilewallet.crypti.me address or so. So...you are saying somebody could use a browser on a smartphone to go to a website run by Crypti. That website could host downloadable executable files. Those executable files could be new / updated smartphone apps. This is all good....but how is this any different from what a non-blockchain-based website can do now? It is not a decentralized solution and the mobilewallet.crypti.me website can be DDoSed or seized by the FBI or just go down from a single server outage. I think it would be better if the Apple App store, the Android Play store, GitHub, the XCR webwallet at mobilewallet.crypti.me, and many other locations stored a single app (written for many computer and smartphone OS) and that single app was used as the gateway for many / all other XCR-based apps stored on decentralized XCR sidechains. Isn't there a difference between using a website to distribute downloadable apps and using XCR sidechains to distribute downloadable apps? (Can we) / (Don't we want to) provide such a sidechain app download capability? Note that the app I am proposing doesn't directly use cryptocoins as a payment / token mechanism and so presumably would not be objectionable to A&A. It would only access data on a blockchain. |
|
|
|
|
Let me start a rambling discussion on the upcoming XCR custom blockchain capabilities.
According to several posters here, the Apple and Android (A&A) app stores are apparently unfriendly to cryptocurrency apps. If so, there needs to be an alternate way to distribute cryptocoin apps outside of the Apple and Android ecosystems. So, is it possible to create an app for both A&A that would take the contents of a new Crypti side chain, validate it as coming from a trusted or previously utilized source, and then load that side chain data as a new or upgraded existing app that would be run on an A or A smartphone?
Basically I am proposing that we at XCR only need to get a single app accepted by A&A, which would be a "plain vanilla" XCR side chain code loader app. This would allow all other apps using XCR to be accessed and downloaded not thru A&A but from new XCR side chains. This vanilla XCR app, once loaded on a smartphone, could then watch for new XCR side chains (and thus new XCR apps) and alert the user when new XCR-specific apps were available. This would allow the (anonymous?) publication of new XCR apps, prevent censorship of apps by A&A, and keep new XCR apps from being lost in the daily noise of all other apps routinely added to the A&A App Stores.
Is this doable? A reasonably good idea?
|
|
|
|
Crypti is Javascript dev platfrom which offer Javascript API to work with Crypti Public Blockchain and ability to create custom private blockchains / Dapp Master Nodes for setting up dapps/private currences/services. It's also a publishing platform.
I am not a JavaScript app programmer and I am wanting to learn. Anybody have advice on where / how to start? I have been looking at Meteor. Anybody have an opinion on whether Meteor would be a good platform or a bad platform to use in developing Crypti dapps? https://www.meteor.com/They seem to have some good app development tutorials for beginners: https://www.meteor.com/tutorials/blaze/creating-an-app |
|
|
|
Thank you Mal. As you already know 0.3.1 + Lite Wallet is out within the next 2 weeks.
I have been waiting to get Crypti Lite 0.3.X on my "secure quarantine" laptop before casting my votes for our current standby delegates. Maybe I'm being overly paranoid, but I just don't like running the passcodes for my big accounts through an online server node. Not even my own online server node. So you standby delegates, please have patience, there are votes from me coming your way soon. |
|
|
|
i really wonder why XCR capitalisation is not at 5 million yet ...
just gotta wait for fresh investors Yes, we need new people. So you all need to spread the word about Crypti as much as you can. The price will rise quickly, once the bull run starts. The new whitepaper looks great. I am going to wait a little longer for the 0.3.0 Crypti Lite to come out, and then I am going to invite around 130 new people to set up Delegate nodes. These are guys who have previously set up DPoS nodes (most with Raspberry Pi) in response to recruitment drives at Peercoin and BitShares. |
|
|
|
Max will you show us whitepaper today? I mean not a blank piece of white paper, but technical whitepaper with technical words  I am very interested in this too. I hope to start talking about specific capabilities to be coded for smart contracts and custom blockchains. These are projected 0.4.0 capabilities that will become available in the next three months, right? |
|
|
|
|
Sigh. My dialogue with Cryptsy about my support ticket request on the XCR 0.3.0 wallet:
June 25:
Guys, PLEASE give some sort of indication when you will have the new Crypti client installed and allow routine deposit and withdrawal of this coin. It has been MONTHS and CRYPTI IS BACK WITH A FUNCTIONAL CLIENT.
I have escalated your inquiry to our technical team. I will let you know as soon as I have an update from them as to when XCR will be back online.
If you have additional questions, please let me know.
Sincerely,
Phoebe
Cryptsy.com
June 30:
Our Support Rep has indicated that your Ticket (#193320) has been Resolved.
If you believe that the ticket has not been resolved, please reply to this email to automatically reopen the ticket.
If there is no response from you, we will assume that the ticket has been resolved and the ticket will be automatically closed after 48 hours.
Sincerely,
TicketsSupport Team
July 1:
Regarding ticket #193320, can you please explicitly confirm that deposit and withdrawal of Crypti (XCR) using the 0.3.0 client is now supported At Cryptsy? Thanks!
Thank you for making a follow-up.
Crypti wallet is still offline and our technical support team is currently working on an update. My apologies for we are unable to confirm the information you require until the coin's wallet is up. However, I can send you a note as soon as wallet is our of maintenance mode. Will this work for you?
Sincerely,
Karen
Cryptsy.com
Yes, please send me a note as soon as the Crypti (XCR) 0.3.0 wallet is out of maintenance mode.
Sigh. You know they won't.
|
|
|
|
I wrote BTER, Poloniex and Cryptsy support. While Cryptsy will likely not answer, I think the others will. Let's see, I will keep you posted. I wrote Cryptsy support again too. We really need to get their attention somehow and get this resolved... |
|
|
|
Once we have a higher market cap and steady volume I hope that more serious exchanges will accept XCR. The market cap cannot change if there is currently no exchange where you can deposit and trade XCR. So it's a chicken/egg problem. This is why I've pushed Coinomat lately. Any feedback on when Cryptsy will get back on board with Crypti? |
|
|
|
For what it's worth, it looks like there are at least 12 Top Delegates in the "101 Club" that are not currently forging:
UPTIME DELEGATE
72.78% Altocumulus
72.78% Altostratus
84.69% Stratocumulus
84.47% Stratus
56.18% foundation10
56.60% foundation9
85.38% MatthewDC_D1
85.07% MatthewDC_D8
12.79% stasDelegate1
12.63% stasDelegate4
75.38% landgraf.paul
53.15% Wulfcastle
This list may be longer, but if so, it's among members whose total uptime is over 85%.
I was wrong, all of these are apparently forging OK. I checked today and uptime on all of these are higher today that when I made the post above, even tho their uptimes declined over a short period of time (obviously less than two cycles) when I made my initial check yesterday. Sorry for the confusion. |
|
|
|
Does anyone know how much blocks does it take to transfer XCR to Poloniex? Transferred a test amount 15 minutes ago, so 90 blocks ago, and it still has not arrived.
Did your Crypti account balance actually go down by the amount you expected? Look here: http://cryptichain.me/Do you see your transaction? If yes, then apparently Polo has yet to manually credit your account there. If no, then your test transfer didn't work and you need to try again. |
|
|
|
Very strange, my uptime went a bit up in the last days. So I encountered the exact contrary phenomenon.
Your uptime SHOULD go up "a bit" over a period of a few days, right? And asymptotically approach 99.99%. My question is, how do you know if you've missed a forge you were supposed to do in a cycle of 101 blocks? Yes. You can check in the forging center if you forged the block or missed it. The interval of your forged blocks should always be between 0 and 101 (1 and 100). I've checked my data for the last eight hours and looks like I'm hitting 100%. However, I think the actual "good" interval is not between 1 and 100 but instead between 1 and 200. You could theoretically be the first forger in cycle A and the last forger in cycle B and there could be 200 blocks between those two turns. A long stretch like this could also account for your "uptime" going down slightly during a two cycle period. I will need to re-evaluate my list of 12 printed above tomorrow when there is a longer period of time to examine. |
|
|
|
Very strange, my uptime went a bit up in the last days. So I encountered the exact contrary phenomenon.
Your uptime SHOULD go up "a bit" over a period of a few days, right? And asymptotically approach 99.99%. My question is, how do you know if you've missed a forge you were supposed to do in a cycle of 101 blocks? |
|
|
|
On my 0.2.0 delegate node when I click on 'Stop Forging' button it asks for a password, entering my delegate passphrase there gives me 'Access denied' error ? I'm not able to stop my delegate and update it to 0.3.0 version.
Please help.
Go to your server, stop the 0.2.0a program / process, copy the blockchain over to the 0.3.0 folder, go to the 0.3.0 folder, mod the config.json text file with your forging account password, and start the 0.3.0 program/process. Don't worry about gracefully doing a controlled transfer between the two versions. Just kill the old job and start the new job. |
|
|
|
|
Show Posts
