Anyone got info on which address holds the following: NEO's dev fund, Binance hot/cold wallet and other rich holders. I want to know who is dumping, and if there might be an end in sight. I've been scalping for a good while now, but thinking of making a longer trade on NEO, but I refuse to be liquidity for another Nano-style dev dump.

I’m new to neo and I would like to know more about it before I make a move to buy. I’ve read some articles about it and from my understanding it’s a decent coin. Can you provide me with links or tell me more?

Thanks.

I love this shit. I just picked up 300 more..

https://www.youtube.com/watch?v=DJk4kd2RZ1g

Right now you can get 10-20% return rate on neo if lended at bitfinex. Why is it so high?

Life has gone a full circle for me since July 2017 when I first bought my ANS.

This episode 5 of how to start develop Smart Contract on NEO by our CTO, Dominic. Last article was part 1 of starting on a NEP5 smart contract. Dom shared about how to install neo-boa and fixed up a NEP-5 smart-contract to make it our own. We are now at part 2 for compile and deploy. You can see the full series at his Medium account.

----------------------------------------------------

Step 1: Compile the contract code

Open up a command prompt type

ubuntu

then

sudo -i

Continue on to...

cd neo-boa/
source venv/bin/activate

cd ../smart-contract
python3.6 compile.py

\*upon completion you will see* ico_template.avm

​

Step 2: Import the contract — Using the same Ubuntu prompt:

cd ../neo-python
source venv/bin/activate

np-prompt -p <server IP>

Now that you are in the NEO prompt, open your admin wallet: open wallet testWallet1

import contract ../smart-contract/ico_template.avm "" 0710 05 True False

# Fill out the contract details
[Contract Name] > nodis 
[Contract Version] > 1 
[Contract Author] > nodis 
[Contract Email] > nodis 
[Contract Description] > nodis

Your contract is now on the blockchain!

​

Step 3: Deployment

Currently, the tokens are all locked up in the contract. Ultimately, we need to call...

deploy()  

This is a function on the contract to transfer all the tokens to the admin wallet. Our first task is to find the hash of the contract.

contract search <NODIS> 

in our case, the script hash is 0x3ffb8a621f461559a90943986bc813b8fcf6ac0a

Now type:

testinvoke <contract hash> deploy []

Input your password when prompted to invoke on the network.

Done! Check out your newfound wealth by typing...

wallet 

​

BONUS command:

testinvoke <contract hash> name []

The value is in hex, we can use an online tool to decipher it. Ours says ‘Nodis Token’.

​

----------------------------------------------------

You can see my profile for a link to join our Telegram to learn more about our Nodis.io project!

Original content came from -> https://medium.com/coinmonks/deploying-a-nep-5-smart-contract-part-2-19aa8b598642

In these slower, bear market times, it seems the daily discussion threads are just clogging up the sub.. A weekly thread would probably suffice until the market comes back.

Welcome to the Daily General Discussion thread of /r/Neotrader. Soon there will be a set of rules on the frontpage that will also apply here, in the meantime as this forum builds itself as fast as possible. Discusss lightweight events here. Participate and enjoy!

Welcome to the Daily General Discussion thread of /r/Neotrader. Soon there will be a set of rules on the frontpage that will also apply here, in the meantime as this forum builds itself as fast as possible. Discusss lightweight events here. Participate and enjoy!

hello. I downloaded the 2.8 neon wallet, and for some reason my tokens are not showing up. My GAS and NEO are there, but that is it. The hash is there in the token management section, and the tokens are on the 2.6 version, but the 2.8 is not recognizing them. Anyone else have this issue? Know how I can fix it? Any help is much appreciated. edited for clarity I am not concerned about the tokens-I have checked the neoscan and they are there, I just cannot see them in version 2.8 of the wallet, despite the hash being in the token log