[ANN] BEAM | Mimblewimble | Private | Scalable | No ICO | No Pre Mine - page 63.

VoskCoin

sr. member

Activity: 1414

Merit: 487

YouTube.com/VoskCoin

https://youtu.be/9UlNfhoRPWU

Here's my video guide on how to mine BEAM, I also have a supportive written guide along w/ a ton of other links in the video description. If you use my link to download the miner, you can simply swap the address w/ yours and start hashing.

If you don't trust me, don't download anything and just watch the video Cheesy

ragnar dannesk gold

jr. member

Activity: 32

Merit: 37

Sparkpool currently, sitting at .02478 BEAM.

If anyone is keen to test send/recieve, I have an address at 104b8c579a2faa96af6c1f4f9586faf66db7830aa4276e9ae67cdcea585fbc06b

If you want to test, send some groth there and I'll return it after. (Can addressed I've received from be sent back the amounts without further info?)

lilaj4de

sr. member

Activity: 602

Merit: 250

I did not quite understand this concept of: No address or other private information is stored in the blockchain. In this case how will I prove that I have sent an amount X for a particular user?

SkyDr4k3

newbie

Activity: 146

Merit: 0

1) what miner can i use? nvidia
2) what are the pools?

Thank you

coffeefan

copper member

Activity: 68

Merit: 0

Quote from: ol92 on January 03, 2019, 06:37:39 PM

Quote from: monika12 on January 03, 2019, 06:11:01 PM

I have problem.
When node is starting following the instruction I got mesage-miner key import failed.What is problem?Maybe with sertificate?

I had similar problem : the miner key generated by the windows wallet seems too long with unusual caracters ...
I have started to mine with the pool above.

I actually had the same problem in the first time.
Be careful with how you copy the data in/out in the CMD - re-check with Notepad++ if there are no unnecessary spaces or anything.

ol92

sr. member

Activity: 445

Merit: 255

Quote from: monika12 on January 03, 2019, 06:11:01 PM

I have problem.
When node is starting following the instruction I got mesage-miner key import failed.What is problem?Maybe with sertificate?

I had similar problem : the miner key generated by the windows wallet seems too long with unusual caracters ...
I have started to mine with the pool above.

monika12

newbie

Activity: 4

Merit: 0

I have problem.
When node is starting following the instruction I got mesage-miner key import failed.What is problem?Maybe with sertificate?

solosequenosenada

hero member

Activity: 952

Merit: 542

Freedom dies from suicide

Quote from: sunsofdust on January 03, 2019, 03:53:23 PM

With the diff being so high, are there any known pools available?

I'm here https://beam.sunpool.top

DYOR

Hueristic

legendary

Activity: 3836

Merit: 4969

Doomed to see the future and unable to prevent it

Has anyone got this running in a linux vm opencl?

coffeefan

copper member

Activity: 68

Merit: 0

Quote from: reffi on January 03, 2019, 03:49:21 PM

how to buy?

OTC trading only at the moment. Still pretty dangerous to do with unknown people.
Best bet to mine yourself to accumulate some or to wait until Atomic Swaps are launched.

coffeefan

copper member

Activity: 68

Merit: 0

It's not ASIC coin - the Equihash isn't the same that zCash is using but Equihash 150,5, therefore ASIC resistant + plans to change the algo after 6 and 12 months.

tbearhere

legendary

Activity: 3164

Merit: 1003

Equihash algorithm? ASIC coin.

sunsofdust

full member

Activity: 151

Merit: 100

With the diff being so high, are there any known pools available?

reffi

hero member

Activity: 770

Merit: 500

how to buy?

kurbeks

sr. member

Activity: 1078

Merit: 255

Congrtaz on mainet launch

livada

newbie

Activity: 417

Merit: 0

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

fapar

sr. member

Activity: 1414

Merit: 270

Undeads.com - P2E Runner Game

Quote from: livada on January 03, 2019, 01:09:36 PM

Quote from: livada on January 03, 2019, 10:31:35 AM

Quote from: BeamPrivacy on January 03, 2019, 09:27:05 AM

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 Sad

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

newbie

Activity: 417

Merit: 0

Quote from: livada on January 03, 2019, 10:31:35 AM

Quote from: BeamPrivacy on January 03, 2019, 09:27:05 AM

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 Sad

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 ?

donnyespo

hero member

Activity: 827

Merit: 1000

Twitter: @bitcoin_dad

any pools out?

Mihawk

sr. member

Activity: 1149

Merit: 347

Quote from: Realitaz on January 03, 2019, 10:56:59 AM

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.

Topic: [ANN] BEAM | Mimblewimble | Private | Scalable | No ICO | No Pre Mine - page 63. (Read 77231 times)