Pages:
Author

Topic: [ANN] [RPX] Red Pulse Token – Next Generation Intelligence and Content Ecosystem - page 74. (Read 81136 times)

full member
Activity: 280
Merit: 100
This is fucking with us! Is his fault and he don't do anything!

is it a scam?
newbie
Activity: 8
Merit: 0
This is fucking with us! Is his fault and he don't do anything!
sr. member
Activity: 432
Merit: 250
neo icos are hard capping like crazy. will be interesting to watch
legendary
Activity: 1400
Merit: 1000
RPX statement is weak asf.

A lot of people bought NEO due to the ico and now you're screwed. Accepting NEO for the ico is a pump attempt and screwing up the ICO time-stamp is another attempt to force people to dump the neo for loss.

If you bought $50k worth of NEO for the ico, you already lost $10,000 and this shit will dump to $20 or less by the time you got your refund.


Red Pulse Team should have open source the contract code and be precise about the time stamp.


Give block 1445025 their RPX token.
newbie
Activity: 2
Merit: 0
They didn't say anything, just talking usual birocratic garbage. Shame on them.
hero member
Activity: 669
Merit: 520
RPX Sale
Official Statement on
2nd Contribution Period


I know there's been a lot of frustration and unhappiness regarding start of the second period of our RPX sale. As stated previously, during this first period, the cap was set at 1,000USD (27 NEO). At the conclusion of this first hour, the cap was lifted to 50,000USD (1,352 NEO). Consequently, many people who wanted to invest more, waited until the second period to invest more.

People who contributed NEO as part of block 1445025, were not considered by the smart contract to be part of the second period of participation yet. However, those that were part of block 144026, and going forward, were included. The reason for this is because smart contract timestamps are deterministic, meaning that it must output the same result, given the same input. In NEP-5 standard, the code used is:

uint now = Blockchain.GetHeader(Blockchain.GetHeight()).Timestamp;

Executing this line gets the timestamp of the PREVIOUS block, because that is the only way all the nodes can agree on what "now" actually means, since the current block 1445025 was still in progress. For everyone that contributed as part of block 144025, the "now" parameter was returned as 2017-10-08 13:59:50 GMT, outside the window of the second period. When the next block 1445026 began, the "now" parameter was then returned as 2017-10-08 14:01:44 GMT, which is within the window of the second period.

Regarding automatic refunds, we were unable to do this as a refund function could only be accomplished with implicit transaction outputs. The NEO blockchain was not designed to have implicit transaction outputs for global assets (such as NEO), because it would bring a number of problems and risk to the SPV protocol. After consulting with the NEO core dev team, the next steps for them are: NEO will provide a trigger mechanism, so that future smart contracts can refuse a transaction upon receiving a global asset transfer at a certain condition. This way, there is no need for refund, because the asset would not be accepted in the first place.

For Red Pulse our next steps are to focus on refunds. I understand the sensitivity regarding having your NEO tied up, so I'm prioritizing the refunds above all else, and personally working around the clock to process them. I aim to have these completed within a week.

Thank you everyone for your understanding, and I apologize for any misunderstanding and inconvenience caused.


Best regards,
Jonathan Ha
Founder & CEO, Red Pulse
full member
Activity: 322
Merit: 107
newbie
Activity: 23
Merit: 0
By looking at ur profile it doesn't seem that there is any scam.
Looking forward to enroll with you.

Thanks for sharing this valuable concept with us.
newbie
Activity: 3
Merit: 0
Also lets see if the SFC thinks you slack-only announcement can be considered insider trading. I swear if my funds are not back immediately I will do everything to shut you down.
newbie
Activity: 3
Merit: 0
I am speaking with my lawyers in HK, I WILL BE SUING if the Neo are not back right away in my wallets. Garbage ICO, scammed lots of investors to have your invite-only slack friends participating. Well done, hope you go underground after ICO.
full member
Activity: 238
Merit: 100
i think people would not be that angry if the contract would have refunded the funds, which exceeded the cap, automatically. this - "may take several weeks"-announcement is what i dislike the most of this, as i dont care not that much any more about RPX.

its almost the same thing as with chainlink ICO. i dont know why companies are in for ICOs but fail so miserable on the execution of them.

anyways hope we get refunded as fast as possible.

I totally agree with you, it should have been blocked for accepting funds whenever no contribution was impossible due to end of ICO or if contributed twice or something. Shouldn't be that hard to program that in a smart contract.
member
Activity: 116
Merit: 10
Quack.
i think people would not be that angry if the contract would have refunded the funds, which exceeded the cap, automatically. this - "may take several weeks"-announcement is what i dislike the most of this, as i dont care not that much any more about RPX.

its almost the same thing as with chainlink ICO. i dont know why companies are in for ICOs but fail so miserable on the execution of them.

anyways hope we get refunded as fast as possible.
full member
Activity: 210
Merit: 100
i felt bad because i only got 27NEO worth of RPX tokens (35100) but there are a lot of people who got nothing. The only thing bothering me now is that the refund of my NEO exceeding the 27NEO i sent will probably take weeks. They are going to stake it before refunding people. Meanwhile NEO will drop to $15 because of btc HF causing Alts to bleed out for a while.

I was send second, transaction not confirmed yet - see that is end, and go in neotracker and send to another exchange and sell there...
newbie
Activity: 41
Merit: 0
hero member
Activity: 669
Merit: 520
As a matter of fact, I would like to tell everyone here that I failed in 2nd round of ZRX(0xproject) as well as Kyber.Network (KNC) but I never complained, why because my funds were not frozen/taken in their custody.

I would not be complaining if my $NEO wasn't in their account for supposedly failed transaction.

Let's see what do they come up with , and how they resolve this matter.

They also have facebook & twitter for notification, but I cannot find their tweet or facebook msg anywhere saying change of plan in 2nd round timing. Their link to join slack on their website [ https://coin.red-pulse.com/slack/ ] still suggest to look for twitter, facebook, and bitcointalk forum (I don't think they announce change of their plan/timing anywhere on those official channels)

[We are currently not accepting any new members to the Slack group. In the meantime, please connect with us over on our official Facebook, Reddit, Twitter, or BitcoinTalk forum.] == https://coin.red-pulse.com/slack/

Let's wait for some words from Red Pulse team, and see what approach they take to resolve this matter.
full member
Activity: 185
Merit: 100
I'm fairly disappointed as well about how the ICO second phase went (i am in block 25).
Let's wait for an official statement from the team first. However i'm afraid people in block 25 will not get tokens. In any case there were much more transactions in block 25 than in 26, so even if they rectified, most of the people in 25 would still get nothing, but at least it would be fairer.
full member
Activity: 140
Merit: 100
When its hitting exchange?
full member
Activity: 210
Merit: 100
I was in Block 25 as well. I'm really looking forward to the statement of the official Red Pulse team. Maybe we receive additional tokens. At least that's my wish
It's not fair to change the rules within 5 minutes in slack, where almost nobody was involved  Huh
newbie
Activity: 1
Merit: 0
i was in block 25 too... would really like rpx rather than neo back
newbie
Activity: 28
Merit: 0
What a disaster. Glad I sat this one out.  Tongue
Pages:
Jump to: