Topic: [XCR] Crypti | Dapps | Sidechains | Dapp Store | OPEN SOURCE | 100% own code | DPoS - page 202. (Read 804701 times)

That is most likely where we would do the chat. We would just be setting a date / time so I could make sure enough of the dev team was available.

This could be done by someone who wanted to setup cloud servers for others, but the cost of cloud servers would have to be taken into consideration to keep the business profitable. Right now, with the low volume and transaction fee rewards on the network, I don't know what that profitability equation would look like.

With the current resource usage, it requires a more expensive cloud node to run the software effectively and the cost might be a little high. Boris is working right now to transition and test the new DB and other changes to tweak the resource usage and get the RAM requirements down. We see this as a major area that needs optimized.

Nice to see you guys involving the community in it.
for any kind of chat about crypti, there is also the cryptitalk irc channel( it's usually just me and karmacoma talking there though)

Thanks for all of the feedback guys. Mike actually came up with the general outline for option #2 and we have been discussing it internally on a daily basis to weed out some of the details. That being said, I would like to let Mike explain and answer questions to make sure you get the most accurate answers you can.

What I would like to do is gauge interest in a community chat. So if I could get myself, Mike, and a few of the others available at a given time to brainstorm and discuss option #2 (as well the other options), would anyone be interested in joining a chat room and shooting around ideas / asking questions directly? I think it would help explain the options as well as maybe help us think of some things we might have missed.

In the meantime, I have created a discussion thread at CryptiTalk that includes a poll. I would like to move the discussion there in regards to the 3 options proposed and also have you all vote on your favorite solution. You can find the new thread here: http://cryptitalk.com/index.php/topic,185.0.html Thanks!  

Edit: As noted by Litoshi, you must be logged in to CryptiTalk to vote on the poll. The radial buttons will not show up if you are not logged in.

I know it very well and I havent said that they would use just 1 machine. I don't care how they would handle that, this is service and you pay fee just for their own solutions.
Look at getclouder.com for example. They can handle as many new ip addresses as you need.

Same problem is when you use cex.io or other cloud mining services or buying hashing power.

The CRYPTI NODE REWARD PROGRAM is up and running.  You should see forging earnings in your wallet now.

Each node has to have a unique IP.  Running 100 computers on the same IP is still just one node.

The birth of "Cloud Forging"  

The problem with this is that you would have to entrust your crypti to a third party, which would have full control of it

I would like to see a website with service that you can deposit lets say 100k Crypti and it would create 100 nodes 1000 XCR each forging together. Such a service could take lets say 1% from what your nodes would forge. I suppose it will happen sooner or later.

Please take the tilecoin shiling somewhere else

guys,XTC is only 1k sato.

please dump this scam coin and all in XTC.

any progress after got some many btc? nope.

+1

Thanks for the update GreXX. This is a welcome boost to the community morale.

Thanks for the update GreXX, I'm going for either Solution 2 (The New Proposal, which I really like the sound of) or 3 (Current PoT implementation).

I'm against Solution 1 (Master Nodes) as it partially centralizes the network.

Just a few quick questions about Solution 2 :

- How long will block times be increased by?
- How long will it take to complete development on Solution 2 if chosen?


Also how much longer till Custom Blockchains can be implemented?

I'm for temporary solution to become permanent one.

 

The contractor in charge was 4 days late with his proposal and his response was that he had another job that ran over and he would get us an answer ASAP. Unfortunately we still have no answer from them in regards to their ideas, solutions, etc.

o 2 week waste what have you nothing! just talked some solutions? HAHAHAHAHAHAHAHAHAHHAHAHAHAHAHAHHAHAHAHAAHAHAHAHAHAHAHAHHA

september.. nothings
october.. nothings
November?  


AHAHAHAHAHHAHAHAHAHAHHAHAHAHAHHAHAHAHAHAHHAHAHAHHAHAHHAAHHAHHAHHAHAHAHAHAHHAHAH AHAHAHHAHAHAHAHAHAHHAHAHAHAHA


i LAUGH so HARD haahahaa


this is the BEST dev team EVER!

.. at talking

HAHAHAHAHAHAHAHAHHAHAH

....aaaaaaaaaaaaaHAHAHAHHAHAHAHHAHAHAHAHAHHAHAHA


weekly meetng: ok we dont do anything for 2 week ok how change this blog so it look like do something

you are PATHETIC and USELESS

hahahha i only camed here to LOL u dont dissepoint! HAHA

i can make u update in 2 weeks hi. we discuss solutions and then had a conference business CEO president meeting to stroke our dicks we discussed 10 differnet pot solutions some where relly interesting discussion we not make the desision or work but if you stay another month here 0.6 XCR

AHAHAHAHHA

this team bring so many laugh for me


i will camed here to laugh you every update because u do nothing HAH dumbass!

LOL ur lead dev gonna travel when ur shit dont even work AHAHAHHAHAHAHAHAHHAHAHAHAHAHHAA

AAHAHHAAHAHHAHAH

maybe rest of team should go to asia to get chinese investors LOL?  


AHAHAHHAHAHAHHAHHAHAH


real Update: we fuck up pot now we do nothing but talk

I think the second PoT solution you proposed is the given choice. Altough I think you should also try to make the temporary solution better in the meantime, as it might take some time to finalize the permanent one, if you even finish it at all.

Thanks for the update.

Development Update

The promised update is live on our blog with updates on PoT Forging, Custom Block Chains (CMB), Bounties, our new Node Reward Program (NRP), Development Team Hiring / Office, and the web re-design. Read it here: http://blog.crypti.me/development-status-update/