[old thread] - RISE | DPOS | APPS & DAPPS

[outfitsoul]

I know this has been mentioned before I'm a supporter of leaving at least a few days between when the ICO ends and when coins are released. It builds anticipation, the market has a chance to start discussing price point and as much as people omg omg Yobits, it still advertising the project. I also hope to see PR company in full swing at least a week before ICO ends.  Lisk did it, Waves is doing it although less than a week apart.

Those are my winter wonderland dreams. ICO investments have always been my main focus.

I think at least a couple weeks.

[1714637302]

1714637302

[1714637302]

1714637302

[1714637302]

1714637302

[jdr0dn3y]

"how are we going to transfer our RISE units to exchangers and how can we withdraw it?"

this is the everyday question i encounter with my referrals. can someone here please tell me the simplest answer to this question. thank you!


and what is the purpose of this   https://risevisionfoundation.atlassian.net/wiki/display/RISDOC/Delegates
I can't understand the purpose of this..

Until the ICO ends, you cannot withdraw or exchange your RISE units. As soon as the ICO is complete, we should start appearing on local exchanges, and your profiles will be updated to create an account on our Mainnet for you, so you have access to your RISE. Once the exchanges setup accounts, it won't be an issue for you to transfer your RISE to the exchanges.

Delegates are part of the security of the system. Delegates provide the same function for us that Miners do for Proof-of-Work cryptocurrencies, like Bitcoin.

In order to be a delegate, you have to sign up to be one, and configure a node for forging. Once you have done that, you need to get enough votes to become a delegate. On mainnet, that means getting more than 100 votes to start with, and once things get going, more votes than however many the 101st delegate has. This allows you to forge (our equivalent to mining), and confirm transactions on the blockchain.

[TravelsAsia]

I know this has been mentioned before I'm a supporter of leaving at least a few days between when the ICO ends and when coins are released. It builds anticipation, the market has a chance to start discussing price point and as much as people omg omg Yobits, it still advertising the project. I also hope to see PR company in full swing at least a week before ICO ends.  Lisk did it, Waves is doing it although less than a week apart.

Those are my winter wonderland dreams. ICO investments have always been my main focus.

I think at least a couple weeks.

That anticipation is key.

[Dajackal]

Rise Documentation Update

Details on how to configure your node to run a delegate.

Delegate Configuration

wow great!
good job guys 

Nice. I think I may take the leap and pick up some today.

[shogdite]

Investment Statistics #16

Comparison of the ICO investment and user base numbers showing approx 24 hours ago until now (time of this post).

Users: 3618 to 3756 = 138 Newly registered signups on rise.vision

Total Btc invested: 642.73 to 672.72 = 29.99 extra Bitcoin raised for RISE development.

Individual Investments: 3358 to 3494 = 136 more investments made.

Out of the 3494 individual investments, 2040 were referred.


For yesterdays stats: https://bitcointalk.org/index.php?topic=1445947.msg15123164#msg15123164

How soon after coin sale will Rise be trading and on what exchanges?

That all depends on how soon the exchanges want to add us.

With the release of mainnet on the 24th (end of ICO) there's a high chance Rise will become tradeable soon after.

Hmm so no exchanges lined up yet? One of the main reasons I put 14 BTC into lisk is because they had polo lined up straight away. A decent exchange is crutial to getting a good value of the coin after launch as it gives people confidence in the coin. If any exchanges come up then I may dip my toes in more than 0.1BTC

Also I can not find the recording from yesterday.. Does anyone have a link please?

I find that hard to believe you had inside information that allowed you to know they had poloniex lined up!?? I would have confidence that bittrex will have it added fairly close to launch. Risevision 136 new investors is such a short time frame is awesome isn't it.

I think RISE is most better, than LISK. RISE has a big potential.

They both have wonderful potential and I share my eggs and never have them in one basket. Its the main reason I found RISE and I am glad I did as competition breeds winners on both sides.

[Tripjammer]

Rise should take off after waves launches....

[Darkoth89]

Awesome ฿ 0.00000774 BTC/RISE Has been increasing steadily each day! 

[wendy107th]

i think it will be next expanse

I hope with same amount of token coins lol and same price  

[placebo]

Awesome ฿ 0.00000774 BTC/RISE Has been increasing steadily each day! 

15 days left and we will hit the moon

[cointrader83]

Rise Documentation Update

Details on how to configure your node to run a delegate.

Delegate Configuration

Doesn't work.

Would you mind explaining in detail what part you were unable to get to work?

Thanks!

Full of bugs:

Code:

[color=red]
npm WARN optional Skipping failed optional dependency /forever/chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: fsevents@1.0.12
npm WARN deprecated graceful-fs@1.2.3: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
npm WARN deprecated wrench@1.5.9: wrench.js is deprecated! You should check out fs-extra (https://github.com/jprichardson/node-fs-extra) for any operations you were using wrench for. Thanks for all the usage over the years.
npm WARN deprecated jade@0.26.3: Jade has been renamed to pug, please install the latest version of pug instead of jade
npm WARN deprecated graceful-fs@2.0.3: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
npm WARN prefer global marked@0.3.5 should be installed with -g
npm WARN prefer global jshint@2.9.2 should be installed with -g[/color]

and

Code:

npm ERR! Linux 3.13.0-042stab113.11
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install"
npm ERR! node v6.2.1
npm ERR! npm  v3.9.3
npm ERR! code ELIFECYCLE

npm ERR! libpq@1.8.2 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the libpq@1.8.2 install script 'node-gyp rebuild'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the libpq package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs libpq
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls libpq
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /rise-core/npm-debug.log

and this:

Code:

psql: could not connect to server: No such file or directory
        Is the server running locally and accepting
        connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?
psql: could not connect to server: No such file or directory
        Is the server running locally and accepting
        connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?
psql: could not connect to server: No such file or directory
        Is the server running locally and accepting
        connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?

[Edkemper]

hope it will stay lower than 3000 sat when the ico is over, and then will have a big rise

[NoBit]

Is there a technical explanation of DPoS somewhere?

[jdr0dn3y]

Full of bugs:

Code:

[color=red]
npm WARN optional Skipping failed optional dependency /forever/chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: fsevents@1.0.12
npm WARN deprecated graceful-fs@1.2.3: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
npm WARN deprecated wrench@1.5.9: wrench.js is deprecated! You should check out fs-extra (https://github.com/jprichardson/node-fs-extra) for any operations you were using wrench for. Thanks for all the usage over the years.
npm WARN deprecated jade@0.26.3: Jade has been renamed to pug, please install the latest version of pug instead of jade
npm WARN deprecated graceful-fs@2.0.3: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
npm WARN prefer global marked@0.3.5 should be installed with -g
npm WARN prefer global jshint@2.9.2 should be installed with -g[/color]

and

Code:

npm ERR! Linux 3.13.0-042stab113.11
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install"
npm ERR! node v6.2.1
npm ERR! npm  v3.9.3
npm ERR! code ELIFECYCLE

npm ERR! libpq@1.8.2 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the libpq@1.8.2 install script 'node-gyp rebuild'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the libpq package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs libpq
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls libpq
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /rise-core/npm-debug.log

and this:

Code:

psql: could not connect to server: No such file or directory
        Is the server running locally and accepting
        connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?
psql: could not connect to server: No such file or directory
        Is the server running locally and accepting
        connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?
psql: could not connect to server: No such file or directory
        Is the server running locally and accepting
        connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?

Thanks for this report

The initial deprecated warnings will be cleaned up with an update early next week.

The second and third error are actually the same thing. I'm working on the issue already. It's a mismatch with postgresql's versions and some dependencies for it.

[shogdite]

Investment Statistics #16

Comparison of the ICO investment and user base numbers showing approx 24 hours ago until now (time of this post).

Users: 3618 to 3756 = 138 Newly registered signups on rise.vision

Total Btc invested: 642.73 to 672.72 = 29.99 extra Bitcoin raised for RISE development.

Individual Investments: 3358 to 3494 = 136 more investments made.

Out of the 3494 individual investments, 2040 were referred.


For yesterdays stats: https://bitcointalk.org/index.php?topic=1445947.msg15123164#msg15123164

How soon after coin sale will Rise be trading and on what exchanges?

That all depends on how soon the exchanges want to add us.

With the release of mainnet on the 24th (end of ICO) there's a high chance Rise will become tradeable soon after.

Hmm so no exchanges lined up yet? One of the main reasons I put 14 BTC into lisk is because they had polo lined up straight away. A decent exchange is crutial to getting a good value of the coin after launch as it gives people confidence in the coin. If any exchanges come up then I may dip my toes in more than 0.1BTC

Also I can not find the recording from yesterday.. Does anyone have a link please?

I find that hard to believe you had inside information that allowed you to know they had poloniex lined up!?? I would have confidence that bittrex will have it added fairly close to launch. Risevision 136 new investors is such a short time frame is awesome isn't it.

I think RISE is most better, than LISK. RISE has a big potential.

They both have wonderful potential and I share my eggs and never have them in one basket. Its the main reason I found RISE and I am glad I did as competition breeds winners on both sides.

Rise think better than the lisk will

I find that hard to decipher to be honest, brush up on your English. However just be glad their is competition that is the point.

[cointrader83]

Full of bugs:

Code:

[color=red]
npm WARN optional Skipping failed optional dependency /forever/chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: fsevents@1.0.12
npm WARN deprecated graceful-fs@1.2.3: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
npm WARN deprecated wrench@1.5.9: wrench.js is deprecated! You should check out fs-extra (https://github.com/jprichardson/node-fs-extra) for any operations you were using wrench for. Thanks for all the usage over the years.
npm WARN deprecated jade@0.26.3: Jade has been renamed to pug, please install the latest version of pug instead of jade
npm WARN deprecated graceful-fs@2.0.3: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
npm WARN prefer global marked@0.3.5 should be installed with -g
npm WARN prefer global jshint@2.9.2 should be installed with -g[/color]

and

Code:

npm ERR! Linux 3.13.0-042stab113.11
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install"
npm ERR! node v6.2.1
npm ERR! npm  v3.9.3
npm ERR! code ELIFECYCLE

npm ERR! libpq@1.8.2 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the libpq@1.8.2 install script 'node-gyp rebuild'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the libpq package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs libpq
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls libpq
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /rise-core/npm-debug.log

and this:

Code:

psql: could not connect to server: No such file or directory
        Is the server running locally and accepting
        connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?
psql: could not connect to server: No such file or directory
        Is the server running locally and accepting
        connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?
psql: could not connect to server: No such file or directory
        Is the server running locally and accepting
        connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?

Thanks for this report

The initial deprecated warnings will be cleaned up with an update early next week.

The second and third error are actually the same thing. I'm working on the issue already. It's a mismatch with postgresql's versions and some dependencies for it.

Thank you!

[Darkoth89]

Full of bugs:

Code:

[color=red]
npm WARN optional Skipping failed optional dependency /forever/chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: fsevents@1.0.12
npm WARN deprecated graceful-fs@1.2.3: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
npm WARN deprecated wrench@1.5.9: wrench.js is deprecated! You should check out fs-extra (https://github.com/jprichardson/node-fs-extra) for any operations you were using wrench for. Thanks for all the usage over the years.
npm WARN deprecated jade@0.26.3: Jade has been renamed to pug, please install the latest version of pug instead of jade
npm WARN deprecated graceful-fs@2.0.3: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
npm WARN prefer global marked@0.3.5 should be installed with -g
npm WARN prefer global jshint@2.9.2 should be installed with -g[/color]

and

Code:

npm ERR! Linux 3.13.0-042stab113.11
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install"
npm ERR! node v6.2.1
npm ERR! npm  v3.9.3
npm ERR! code ELIFECYCLE

npm ERR! libpq@1.8.2 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the libpq@1.8.2 install script 'node-gyp rebuild'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the libpq package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs libpq
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls libpq
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /rise-core/npm-debug.log

and this:

Code:

psql: could not connect to server: No such file or directory
        Is the server running locally and accepting
        connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?
psql: could not connect to server: No such file or directory
        Is the server running locally and accepting
        connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?
psql: could not connect to server: No such file or directory
        Is the server running locally and accepting
        connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?

Thanks for this report

The initial deprecated warnings will be cleaned up with an update early next week.

The second and third error are actually the same thing. I'm working on the issue already. It's a mismatch with postgresql's versions and some dependencies for it.

Thank you!

I've been emailing (bugging) and working with him about this the past few hours haha

[jdr0dn3y]

Darkoth89 has been very, very helpful working on this.

[cointrader83]

Full of bugs:

Thanks for this report

The initial deprecated warnings will be cleaned up with an update early next week.

The second and third error are actually the same thing. I'm working on the issue already. It's a mismatch with postgresql's versions and some dependencies for it.

Thank you!

I've been emailing (bugging) and working with him about this the past few hours haha

Yes I think a lot of people just said "Cool, thanks, good job" but they didn't tested. 

[cointrader83]

Darkoth89 has been very, very helpful working on this.

Keep up the good work guys!

[Darkoth89]

Darkoth89 has been very, very helpful working on this.

Keep up the good work guys!

jdr0dn3y is the real hero here, i've never seen a dev who responds so quick and provides solutions so promptly.   I'm usually one of those people who's like "yeah cool" and let's other people do the testing, but I believe in this project so helping out as much as I can!