Topic: IOTA - page 403. (Read 1473233 times)

now, I am really curious to know if the iota community members are also invading other projects' threads in order to make propaganda... I hope not 

Yes, Lordoliver may be right, may be wrong. But you are definitely wrong 100%. "Not honest at all"? "hyped by these trolls"? Who are you to make such statements? It is the first time someone calls me a troll, and it is funny the name of that one starts with trolleroo. I know, Internet allows you to feel yourself a macho, but if we were nearby, you would have been more responsible for your statements.

I am invested both in Iota and Byteball, and I have no preference - both of them are very interesting and innovative projects made for different purposes and different targets in mind. If you care to see my posts made recently in Byteball thread - you will see me exactly suggesting not to hijack Iota threads with Byteball hyping. My personal values do not allow me to hype anything in general, I just ask questions, state facts and my honest opinions, and it should be clear from my history. Do your homework before blaming people. Also would be nice if you try to answer real concerns and questions, rather than just standing there like a watchdog protecting Iota where it is not actually needed.

Anyway, I see how my last post could be considered as advertisement, especially now when by some reason Iota supporters are so oversensitive to any BB mention. Lets forget about my questions, moreover they are mostly answered already, thanks to lordoliver's constructive approach and help. I got no answer to my question about ports IOTA use, but thats ok, I will find that myself somehow, its easier and more pleasant than dealing with some of Iota protector house-dogs who do not understand a single bit in technology or network, but like to bite people.

Take care, and relax.

you may be right, you may be wrong, but it is honest of you to give your opinion. but those other two are not honest at all, they are shamelessly trying to make propaganda of their project (as if it would make any difference anyway, because the stupid people who will fall for their "dubious talk" are not at all needed for this project, and will do us a favour if they simply move to the "perfect auto-peer-discovery project" being hyped by these trolls)

If we implemented an optional "isPublicNode" parameter in the configuration, as I already suggested multiple times, everyone can decide for its own, not to stay "hidden" any more.
And this dubious talk would have been not even possible...

  i wonder if advertisement of other projects is not trolling....

I also have Byteball wallet successfully running in a LAN behind a NAT... Actually with Byteball its easy, as it just works. With IOTA it would be tricky, as you have to manually find nodes, which are nowhere publicly available. You have to go to Slack, ask for nodes and somehow make sure you find only peers who run node on machines directly connected to Internet and running public IP address... As you need to find 5-9 nodes of that kind (involving a chat with every other node owner, just to find out whether he runs public IP or not and whether he agrees to connect to node like yours, expect about a week of setup time

I am not complaining, as I understand it is the way it is, and there are good reasons for removal of auto peer discovery and introducing this notorious manual node search instead. For me the tech part is easy, chat part is tiresome. Hopefully light wallet comes soon.

I did not try IOTA, but with byteball there's no problem to run within a subnet, behind the NAT. The nodes communicate well and have no issue. Maybe I should try IOTA for that too.

Call for papers IoT DevCon 2017
Submission deadline - January 31, 2017
Notification of acceptance - February 28, 2017
http://www.iot-devcon.com/callforpaper.php

IoT Developers Conference 2017
April 26-27, 2017
Santa Clara, CA
http://www.iot-devcon.com/

we're building a bigger reddit-community and set up a weekly stickied thread!
please take part in discussions and spread the word!

https://www.reddit.com/r/Iota/comments/5oe1zt/weekly_riota_discussion_share_info_thoughts_ideas/

Thanks for your post and validated for me !! 

Friendly announcement for you traders here:
As a temporary solution, an OTC Bot has been set up to enable trading in the official IOTA slack.
Since @yassinnxt   provided an excellent service as escrow in the past, he will act as an intermediary, before IOTA hits exchanges.
Additional advice: @yassinnxt   is the only escrow. Don't send your funds to different persons and be sure to interact with @yassinnxt   only as impersonators occasionally tried to scam some people in the past.

The OTC-bot service assisted by Yassin works as follows:

1. You send BTC or iotas to an address provided by Yassin (via private message)
2. Yassin executes a command to deposit the accordant amount to your balance tracked by the bot
3. You buy/sell iotas (this can happen as many times as you need)
4. You send Yassin an address to withdraw the earned BTC/iotas
5. Yassin adjusts your balance and sends real tokens to your address
6. Trades are taxed with 0% fee.
7. Deposits/withdrawals are charged with 1% fee (rounded up).
8. Min amount of a deposit/withdrawal is 10'000 microBTC/2 Gi.
9. To get instructions on how to trade iotas once you get your tokens on the balance type "HELP" on #trading   channel.
10. As a precaution, you are advised to provide Yassin with an extra BTC and IOTA-address to be able to receive your funds once you left slack for different reasons, such as a ban or technical issues.
11. For each IOTA deposit, a new address must be generated. This is necessary to show the right balances for each entry listed by the bot.
12. For better usability, Gi and microBTC for fees are always rounded. (1Gi for 2GI-100Gi, 2Gi from >100Gi-200Gi and so on)

The service was tested with test tokens, but it is still possible that an undiscovered bug may lead to a loss of all your BTC/iotas, so we suggest to trade small amounts per session.

Example-trade:

1. Alice contacts @yassinnxt   and says "I want to deposit 50 BTC"
2. She sends 50 BTC to an address provided by Yassin
3. Once 50 BTC are confirmed, Yassin types "GIVE 49.5 BTC TO @Alice (1% fee included)
4. Alice contacts Yassin and says "I want to withdraw 200 gigaiotas (Gi)"
5. Yassin executes "TAKE 200 Gi FROM @Alice"
6. Yassin sends 198 Gi to Alice
7. Alice contacts Yassin and says "I want to deposit 200 Gi"
8. She sends Yassin 200 Gi
9. Once 200 Gi are confirmed he types "GIVE 198 gigaiotas TO @Alice" (1% fee included)
10. Alice contacts Yassin and says "I want to withdraw 50 BTC"
11. Yassin types "TAKE 50 BTC FROM @Alice"
12. Yassin sends 49.5 BTC to her (1% fee included)

Happy trading!

http://www.tangleblog.com/2017/01/16/the-incredible-january/

Approximately 30k btc.

Thanks a lot for the answer! So the two nodes behind different NAT servers have no chance to connect. If I have my PC behind a NAT, and have no access to router to configure it, I have to search for peers running on public machines only...
It looks like people should specify whether whey run public IP or not, when they ask for nodes in nodesharing channel... so there will be less issues.

One more question: lets say I have access to router, so can forward traffic to my PC, but I do not want to forward all the traffic. Which port should I forward, so IOTA wallet can be connected from outside? In other words, which ports IOTA uses? Is it one port or many? TCP or UDP?

Thanks for help. I know if this goes to technical, I'll have to go to Slack...

The nodes outside of the lan don't have to connect to you, if you want run a local node/wallet. They only have to know your public ip in order to "allow" your access.
But the nodes you are connecting to have to be public, of course...

Edit: if you want to make your computer public available you have to configure your routers routing tables.

This is cool. What is the market cap at current price.

You mean - RTFM . Very kind of you . But I see not a single page on those tutorials answering my questions above, or even touching that topic (running without static ip is completely different topic).

Is there anybody here who is familiar with network administration and can answer my questions/concerns?
Or, alternatively, someone, who actually run a node/wallet while being behind a corporate firewall?

I suppose there should be one...

yes, you can run the wallet behind a NAT router http://iotasupport.com/tutorials.shtml

Guys, is my question above too hard to nobody can answer, or it is too stipid, so nobody want to answer..?

I basically ask whether there is a way to have a IOTA-enabled machine running in the corporate LAN, or in a home network behind a NAT router..? How peer-adding needs to be done in that case?

I suppose that is a common scenario, so there should have been discussions about that. Many (I would assume - the majority of) IoT devices will run in a private LAN, being protected by NAT firewall, so botnets cannot infect them. So if we want IOTA wallet to run on them, they need to be able to connect to other nodes outside the LAN, and (the most tricky part) the nodes outside the LAN need to connect to them! With current manual peer-discovery (where the other peer needs real public IP:port to connect) it could be tricky. Opening a static mapping for any single IoT device could be a tiresome task for the net admin. UPNP then? But does IOTA client have a UPNP? Could anyone point me to some discussion or paper about this?

Type   |    Qty (Gi)   |   Price (microBTC/Gi)   |       Amount (microBTC)   |   Owner
--------------------------------------------------------------------------------------
 ASK   |          11   |                18'000   |                 198'000   |   #8 @come-from-beyond
 ASK   |          11   |                17'000   |                 187'000   |   #7 @come-from-beyond
 ASK   |          11   |                16'000   |                 176'000   |   #6 @come-from-beyond
 ASK   |          11   |                15'000   |                 165'000   |   #5 @come-from-beyond
 ASK   |          11   |                14'000   |                 154'000   |   #4 @come-from-beyond
 ASK   |          11   |                13'000   |                 143'000   |   #3 @come-from-beyond
 ASK   |            6   |                12'000   |                   72'000   |   #1 @come-from-beyond
 ASK   |          11   |                12'000   |                 132'000   |   #2 @come-from-beyond
 ASK   |            9   |                11'900   |                 107'100   |   #0 @albert
--------------------------------------------------------------------------------------
 BID   |             7   |                10'500   |                   73'500   |   #0 @allyourbase
 BID   |           50   |                10'300   |                  515'000   |   #0 @achim
 BID   |         100   |                10'200   |               1'020'000   |   #0 @sdannecker
 BID   |           50   |                10'100   |                 505'000   |   #0 @teletobi
 BID   |           18   |                10'000   |                 180'000   |   #0 @radix
 BID   |             7   |                  8'600   |                   60'200   |   #9 @come-from-beyond
 BID   |           13   |                  8'000   |                 104'000   |   #0 @come-from-beyond
 BID   |           19   |                  6'000   |                 114'000   |   #0 @bahamapascal