[ANN] BEAM | Mimblewimble | Private | Scalable | No ICO | No Pre Mine

[BeamPrivacy]

Happy new year Beamers! 2 Days to go before Mainnet!
https://medium.com/beam-mw/beam-a-scalable-confidential-cryptocurrency-based-on-the-mimblewimble-protocol-will-go-live-soon-562b2d6dd727

[1715536741]

1715536741

[1715536741]

1715536741

[1715536741]

1715536741

[BeamPrivacy]

When Crypto 101 meets Beam, we get a comprehensive podcast about Mimblewimble
https://www.listennotes.com/podcasts/crypto-101-the-average-consumers-guide-to-BcNg_JIrd2G/

[Hueristic]

OK, Going to be gone for a week, how do I setup to have miner join a pool on launch?

[BeamPrivacy]

best would be for you to have a look on our Mining Section here: https://beam-docs.readthedocs.io/en/latest/rtd_pages/user_mining_beam.html

[BeamPrivacy]

Tomorrow is the D-Day! "Tomorrow belongs to those who can hear it coming". David Bowie. Do you hear it?

[BeamPrivacy]

#Mainnet is for tomorrow, wanna know what is going to happen? Here you go. https://medium.com/beam-mw/beam-the-road-to-mainnet-6cea54040afc

[BeamPrivacy]

Very interesting and serious video presentation of Beam and Grin.
https://youtu.be/8jAsxmemSwY

[BeamPrivacy]

https://www.youtube.com/watch?v=Lh4jPNUZYi8&t=6s

[BeamPrivacy]

Beam Mainnet is live! Welcome to a new privacy-oriented world!
https://medium.com/beam-mw/mimblewimble-mainnet-release-notes-8766e49e241d

[fapar]

Beam Mainnet is live! Welcome to a new privacy-oriented world!
https://medium.com/beam-mw/mimblewimble-mainnet-release-notes-8766e49e241d

Congratulations on the launch of the main network!
Do I understand correctly that the difficulty of the network is shown in the sol/s? Then it turns out that now in the network mining 1000000 cards ~1080 Ti/2080...

Upd. ~68K cards

[livada]

Beam Mainnet is live! Welcome to a new privacy-oriented world!
https://medium.com/beam-mw/mimblewimble-mainnet-release-notes-8766e49e241d

my nod say this :

929 Node ID=36995604e4c338a3
I 2019-01-03.16:28:10.929 Initial Tip: 0-0000000000000000
I 2019-01-03.16:28:10.930 Requesting block 0-0000000000000000
I 2019-01-03.16:28:10.930 PI 0000000000000000--0.0.0.0 New
I 2019-01-03.16:28:10.931 PI 0000000000000000--0.0.0.0 Address changed to 52.59.22.93:8100
I 2019-01-03.16:28:10.933 stratum server listens to 0.0.0.0:10002
I 2019-01-03.16:28:11.606 +Peer 52.59.22.93:8100
I 2019-01-03.16:28:11.782 Peer 52.59.22.93:8100 Connected
I 2019-01-03.16:28:11.853 Peer 52.59.22.93:8100 Auth. Type=N, ID=935744fb9735c004
I 2019-01-03.16:28:11.854 52.59.22.93:8100 received PI
I 2019-01-03.16:28:11.854 deleted anonymous PI
I 2019-01-03.16:28:11.854 PI 935744fb9735c004--0.0.0.0 New
I 2019-01-03.16:28:11.855 PI 935744fb9735c004--0.0.0.0 Address changed to 52.59.22.93:8100
I 2019-01-03.16:28:11.856 PI 935744fb9735c004--52.59.22.93:8100 connected, info updated
W 2019-01-03.16:28:11.862 52.59.22.93:8100: Incompatible peer cfg!
I 2019-01-03.16:28:11.863 -Peer 52.59.22.93:8100
I 2019-01-03.16:28:11.863 PI 935744fb9735c004--52.59.22.93:8100 Rating 1024 -> 0
E 2019-01-03.16:28:11.865 beam::ProtocolBase::on_new_message int(type)=0 ret=0

i use eu-node02.mainnet.beam.mw:8100

where is problewm ?

tesnet work ok :  --peer=3.1.46.96:8100
this not : --peer=eu-node02.mainnet.beam.mw:8100 - this is adres for home page

i try all this bit not work :


Mainnet IPs
eu-node01.mainnet.beam.mw:8100
eu-node02.mainnet.beam.mw:8100
eu-node03.mainnet.beam.mw:8100
eu-node04.mainnet.beam.mw:8100
us-node01.mainnet.beam.mw:8100
us-node02.mainnet.beam.mw:8100
us-node03.mainnet.beam.mw:8100
us-node04.mainnet.beam.mw:8100
ap-node01.mainnet.beam.mw:8100
ap-node02.mainnet.beam.mw:8100
ap-node03.mainnet.beam.mw:8100
ap-node04.mainnet.beam.mw:8100

[Realitaz]

Any place for OTC trading? If anyone wants to sell, contact me.
(I have another, very old bitcointalk account but I don't want to dox myself ITT)

[leond]

So there are no any integrated gpu miner in desktop wallet?

[Mihawk]

Any place for OTC trading? If anyone wants to sell, contact me.
(I have another, very old bitcointalk account but I don't want to dox myself ITT)

Wait for the launch in some market, it will be possible to get BEAM at prices, currently are inflating OTC prices.

[donnyespo]

any pools out?

[livada]

Beam Mainnet is live! Welcome to a new privacy-oriented world!
https://medium.com/beam-mw/mimblewimble-mainnet-release-notes-8766e49e241d

my nod say this :

929 Node ID=36995604e4c338a3
I 2019-01-03.16:28:10.929 Initial Tip: 0-0000000000000000
I 2019-01-03.16:28:10.930 Requesting block 0-0000000000000000
I 2019-01-03.16:28:10.930 PI 0000000000000000--0.0.0.0 New
I 2019-01-03.16:28:10.931 PI 0000000000000000--0.0.0.0 Address changed to 52.59.22.93:8100
I 2019-01-03.16:28:10.933 stratum server listens to 0.0.0.0:10002
I 2019-01-03.16:28:11.606 +Peer 52.59.22.93:8100
I 2019-01-03.16:28:11.782 Peer 52.59.22.93:8100 Connected
I 2019-01-03.16:28:11.853 Peer 52.59.22.93:8100 Auth. Type=N, ID=935744fb9735c004
I 2019-01-03.16:28:11.854 52.59.22.93:8100 received PI
I 2019-01-03.16:28:11.854 deleted anonymous PI
I 2019-01-03.16:28:11.854 PI 935744fb9735c004--0.0.0.0 New
I 2019-01-03.16:28:11.855 PI 935744fb9735c004--0.0.0.0 Address changed to 52.59.22.93:8100
I 2019-01-03.16:28:11.856 PI 935744fb9735c004--52.59.22.93:8100 connected, info updated
W 2019-01-03.16:28:11.862 52.59.22.93:8100: Incompatible peer cfg!
I 2019-01-03.16:28:11.863 -Peer 52.59.22.93:8100
I 2019-01-03.16:28:11.863 PI 935744fb9735c004--52.59.22.93:8100 Rating 1024 -> 0
E 2019-01-03.16:28:11.865 beam::ProtocolBase::on_new_message int(type)=0 ret=0

i use eu-node02.mainnet.beam.mw:8100

where is problewm ?

tesnet work ok :  --peer=3.1.46.96:8100
this not : --peer=eu-node02.mainnet.beam.mw:8100 - this is adres for home page

i try all this bit not work :


Mainnet IPs
eu-node01.mainnet.beam.mw:8100
eu-node02.mainnet.beam.mw:8100
eu-node03.mainnet.beam.mw:8100
eu-node04.mainnet.beam.mw:8100
us-node01.mainnet.beam.mw:8100
us-node02.mainnet.beam.mw:8100
us-node03.mainnet.beam.mw:8100
us-node04.mainnet.beam.mw:8100
ap-node01.mainnet.beam.mw:8100
ap-node02.mainnet.beam.mw:8100
ap-node03.mainnet.beam.mw:8100
ap-node04.mainnet.beam.mw:8100

any help ?

what peer work ?

i use 3.1.46.96:8100 but not share

Setup OpenCL devices:
=====================
Found device 0: Intel(R) HD Graphics 610
Memory check failed
Device reported 3228MByte memory, 3808 are required
Found device 1: Radeon RX Vega
Memory check ok
Loading and compiling Beam OpenCL Kernel
Build sucessfull.
Found device 2: Radeon RX Vega
Memory check ok
Loading and compiling Beam OpenCL Kernel
Build sucessfull.
Found device 3: Radeon RX Vega
Memory check ok
Loading and compiling Beam OpenCL Kernel
Build sucessfull.

Waiting for work from stratum:
==============================
Connecting to 127.0.0.1:10002
Connected to node. Starting TLS handshake.
TLS Handshake sucess
New work received with id 866 at difficulty 327833

Start mining:
=============
Performance: 13.47 sol/s 13.47 sol/s 14.00 sol/s
Performance: 12.93 sol/s 12.60 sol/s 12.60 sol/s
Performance: 14.60 sol/s 13.47 sol/s 13.20 sol/s
Performance: 13.93 sol/s 12.13 sol/s 15.13 sol/s
Performance: 13.67 sol/s 12.07 sol/s 14.80 sol/s
Performance: 13.20 sol/s 12.67 sol/s 13.87 sol/s
Performance: 13.40 sol/s 13.67 sol/s 14.27 sol/s
Performance: 12.60 sol/s 13.13 sol/s 15.13 sol/s
Performance: 13.53 sol/s 13.80 sol/s 13.87 sol/s
Performance: 13.20 sol/s 12.47 sol/s 13.67 sol/s

this is 3 vega 56- this s normal screen? where is share ?

[fapar]

Beam Mainnet is live! Welcome to a new privacy-oriented world!
https://medium.com/beam-mw/mimblewimble-mainnet-release-notes-8766e49e241d

my nod say this :

929 Node ID=36995604e4c338a3
I 2019-01-03.16:28:10.929 Initial Tip: 0-0000000000000000
I 2019-01-03.16:28:10.930 Requesting block 0-0000000000000000
I 2019-01-03.16:28:10.930 PI 0000000000000000--0.0.0.0 New
I 2019-01-03.16:28:10.931 PI 0000000000000000--0.0.0.0 Address changed to 52.59.22.93:8100
I 2019-01-03.16:28:10.933 stratum server listens to 0.0.0.0:10002
I 2019-01-03.16:28:11.606 +Peer 52.59.22.93:8100
I 2019-01-03.16:28:11.782 Peer 52.59.22.93:8100 Connected
I 2019-01-03.16:28:11.853 Peer 52.59.22.93:8100 Auth. Type=N, ID=935744fb9735c004
I 2019-01-03.16:28:11.854 52.59.22.93:8100 received PI
I 2019-01-03.16:28:11.854 deleted anonymous PI
I 2019-01-03.16:28:11.854 PI 935744fb9735c004--0.0.0.0 New
I 2019-01-03.16:28:11.855 PI 935744fb9735c004--0.0.0.0 Address changed to 52.59.22.93:8100
I 2019-01-03.16:28:11.856 PI 935744fb9735c004--52.59.22.93:8100 connected, info updated
W 2019-01-03.16:28:11.862 52.59.22.93:8100: Incompatible peer cfg!
I 2019-01-03.16:28:11.863 -Peer 52.59.22.93:8100
I 2019-01-03.16:28:11.863 PI 935744fb9735c004--52.59.22.93:8100 Rating 1024 -> 0
E 2019-01-03.16:28:11.865 beam::ProtocolBase::on_new_message int(type)=0 ret=0

i use eu-node02.mainnet.beam.mw:8100

where is problewm ?

tesnet work ok :  --peer=3.1.46.96:8100
this not : --peer=eu-node02.mainnet.beam.mw:8100 - this is adres for home page

i try all this bit not work :


Mainnet IPs
eu-node01.mainnet.beam.mw:8100
eu-node02.mainnet.beam.mw:8100
eu-node03.mainnet.beam.mw:8100
eu-node04.mainnet.beam.mw:8100
us-node01.mainnet.beam.mw:8100
us-node02.mainnet.beam.mw:8100
us-node03.mainnet.beam.mw:8100
us-node04.mainnet.beam.mw:8100
ap-node01.mainnet.beam.mw:8100
ap-node02.mainnet.beam.mw:8100
ap-node03.mainnet.beam.mw:8100
ap-node04.mainnet.beam.mw:8100

any help ?

what peer work ?

i use 3.1.46.96:8100 but not share

Setup OpenCL devices:
=====================
Found device 0: Intel(R) HD Graphics 610
Memory check failed
Device reported 3228MByte memory, 3808 are required
Found device 1: Radeon RX Vega
Memory check ok
Loading and compiling Beam OpenCL Kernel
Build sucessfull.
Found device 2: Radeon RX Vega
Memory check ok
Loading and compiling Beam OpenCL Kernel
Build sucessfull.
Found device 3: Radeon RX Vega
Memory check ok
Loading and compiling Beam OpenCL Kernel
Build sucessfull.

Waiting for work from stratum:
==============================
Connecting to 127.0.0.1:10002
Connected to node. Starting TLS handshake.
TLS Handshake sucess
New work received with id 866 at difficulty 327833

Start mining:
=============
Performance: 13.47 sol/s 13.47 sol/s 14.00 sol/s
Performance: 12.93 sol/s 12.60 sol/s 12.60 sol/s
Performance: 14.60 sol/s 13.47 sol/s 13.20 sol/s
Performance: 13.93 sol/s 12.13 sol/s 15.13 sol/s
Performance: 13.67 sol/s 12.07 sol/s 14.80 sol/s
Performance: 13.20 sol/s 12.67 sol/s 13.87 sol/s
Performance: 13.40 sol/s 13.67 sol/s 14.27 sol/s
Performance: 12.60 sol/s 13.13 sol/s 15.13 sol/s
Performance: 13.53 sol/s 13.80 sol/s 13.87 sol/s
Performance: 13.20 sol/s 12.47 sol/s 13.67 sol/s

this is 3 vega 56- this s normal screen? where is share ?

Yes, for Vega 56 its normal https://beam-docs.readthedocs.io/en/latest/rtd_pages/user_mining_beam.html
Do you see the difficulty of the network? This increase in difficulty is questionable... May be Mimblewimble not so ASIC resistance...

My node start conf:  .\beam-node.exe --port=10001 --peer=eu-node02.mainnet.beam.mw:8100 --stratum_port=10002
 --stratum_secrets_path=. --key_mine=myminekey --key_owner=myownerkey --pass=mypasswordforwallet

[livada]

thx i use your start and now work i think

http://imgbox.com/THPDzYsM

this is normal?

W 2019-01-03.19:45:50.595 221.138.200.4:10000: connection timed out
I 2019-01-03.19:45:50.595 -Peer 221.138.200.4:10000
I 2019-01-03.19:45:50.595 PI 9c5392a914ae27e6--221.138.200.4:10000 Rating 1024 -> 896
I 2019-01-03.19:45:50.736 +Peer 185.210.217.171:10000
W 2019-01-03.19:45:51.595 223.88.151.46:10000: connection timed out


--stratum_secrets_path=.   I must use this ? i start direkt in cmd

[kurbeks]

Congrtaz on mainet launch

[reffi]

how to buy?