Hi, new version has only win64 build?
Will there be win32 build?
I will crank out a 32-bit version for Windows and send it to VegasGuy. |
|
|
|
So, what happened to the new wallet???
Has been staking orphans, since April 1st. Some kinda of April "FOOLS" JOKE???
Griffith might be good, BUT should have run it by Limtex first. NOW WHAT???
Is it because not enough people are not on newest wallet???
Peace, Dennis
A couple errors were made in the rush to change the rewards. You are correct that it should have been a Pull Request back to LIMX. |
|
|
|
I kinda liked the softer blue of the current logos. The new logo is vivid! maybe a little to harse after seeing it many times... or is that the plan? Make people look at the high contrasting logo? Just my personal opinion. No harm meant. new banners will be soon used for advertizements  |
|
|
|
Mac Wallet built from master. The Darksend errors turned out to be due to the string updates, the magic hashing prefix having changed from previous wallets. This is now reverted but can be put back in with the MN reward update as everyone will have to update their wallets then anyway. Here it is: https://we.tl/X8E1cNeEH6Sorry, this did not work out of the box: Process: Lasvegascoin-Qt [9003]
Path: /Applications/Lasvegascoin-Qt.app/Contents/MacOS/Lasvegascoin-Qt
Identifier: io.lasvegascoin.Lasvegascoin-Qt
Version: 2.0.0 (2.0.0)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Lasvegascoin-Qt [9003]
User ID: 501
Date/Time: 2018-02-19 22:29:11.666 -0500
OS Version: Mac OS X 10.12.5 (16F73)
Report Version: 12
Anonymous UUID: FD000EFC-68BC-0238-DD6F-A30A6C9EEE96
Sleep/Wake UUID: 660E1AE6-4A1E-426C-8BA2-0256EF58DCDF
Time Awake Since Boot: 340000 seconds
Time Since Wake: 11000 seconds
System Integrity Protection: enabled
Crashed Thread: 0
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Termination Reason: DYLD, [0x1] Library missing
Application Specific Information:
dyld: launch, loading dependent libraries
Dyld Error Message:
Library not loaded: @loader_path/libboost_system-mt.dylib
Referenced from: /Applications/Lasvegascoin-Qt.app/Contents/Frameworks/libboost_thread-mt.dylib
Reason: image not found
Binary Images:
0x10278d000 - 0x1030bcff7 +io.lasvegascoin.Lasvegascoin-Qt (2.0.0 - 2.0.0) <C96DB1FE-09E2-31B1-B945-2D385981B832> /Applications/Lasvegascoin-Qt.app/Contents/MacOS/Lasvegascoin-Qt
0x10318d000 - 0x10318fff7 +libboost_system.dylib (0) <707D69DD-1F9A-397A-91ED-8514253836BE> /Applications/Lasvegascoin-Qt.app/Contents/Frameworks/libboost_system.dylib
0x103199000 - 0x1031a7fff +libboost_filesystem.dylib (0) <8D43659B-9A93-3E32-B1CB-18CE46AF6746> /Applications/Lasvegascoin-Qt.app/Contents/Frameworks/libboost_filesystem.dylib
0x1031b0000 - 0x1031e4ff7 +libboost_program_options-mt.dylib (0) <BF1E6821-CD8C-3ECC-A085-BB3FA9136E96> /Applications/Lasvegascoin-Qt.app/Contents/Frameworks/libboost_program_options-mt.dylib
0x103202000 - 0x10320ffff +libboost_thread-mt.dylib (0) <38632F95-B295-32D8-B459-43B7C1EBFB62> /Applications/Lasvegascoin-Qt.app/Contents/Frameworks/libboost_thread-mt.dylib
0x10321a000 - 0x10321bffb +libboost_chrono-mt.dylib (0) <D59E68CD-4CC0-3E29-9847-2A7FF25D705A> /Applications/Lasvegascoin-Qt.app/Contents/Frameworks/libboost_chrono-mt.dylib
0x103224000 - 0x103323ff3 +QtNetwork (0) <F905FD2E-6AEF-3E33-8F65-F7068149EC91> /Applications/Lasvegascoin-Qt.app/Contents/Frameworks/QtNetwork.framework/Versions/5/QtNetwork
0x10336b000 - 0x1037b6fff +QtWidgets (0) <D7B3FE21-B24F-37E6-B4B9-96992DB5403C> /Applications/Lasvegascoin-Qt.app/Contents/Frameworks/QtWidgets.framework/Versions/5/QtWidgets
0x103918000 - 0x103d24feb +QtGui (0) <3C92B4B6-FDF7-3E7C-BF6E-F9E6867F19EA> /Applications/Lasvegascoin-Qt.app/Contents/Frameworks/QtGui.framework/Versions/5/QtGui
0x103e1a000 - 0x1042e0fff +QtCore (0) <EC7502C4-83F7-35D4-B30E-0A22156E3366> /Applications/Lasvegascoin-Qt.app/Contents/Frameworks/QtCore.framework/Versions/5/QtCore
0x104390000 - 0x1043eaff7 +QtDBus (0) <1A5ADDB3-D25B-3698-9172-A7379617630F> /Applications/Lasvegascoin-Qt.app/Contents/Frameworks/QtDBus.framework/Versions/5/QtDBus
0x104406000 - 0x104538ffb +libprotobuf.15.dylib (0) <2C6A5B36-5066-362A-91D7-06C58D3480D8> /Applications/Lasvegascoin-Qt.app/Contents/Frameworks/libprotobuf.15.dylib
0x1045ee000 - 0x104712ff7 +libdb_cxx-4.8.dylib (0) <893E0F96-1F8A-3073-B1CF-CC60610C3E90> /Applications/Lasvegascoin-Qt.app/Contents/Frameworks/libdb_cxx-4.8.dylib
0x10474d000 - 0x10478efff +libssl.1.0.0.dylib (0) <06AA97A5-2312-3F36-88B5-95A3A2C2E237> /Applications/Lasvegascoin-Qt.app/Contents/Frameworks/libssl.1.0.0.dylib
0x1047aa000 - 0x1047b2ff3 +libminiupnpc.16.dylib (0) <318CB83F-5197-3DC0-A126-6585DD663927> /Applications/Lasvegascoin-Qt.app/Contents/Frameworks/libminiupnpc.16.dylib
0x1047b9000 - 0x104929c87 +libcrypto.1.0.0.dylib (0) <917EC558-AA0C-35B1-808D-7F2BC1B04ADB> /Applications/Lasvegascoin-Qt.app/Contents/Frameworks/libcrypto.1.0.0.dylib
0x10d228000 - 0x10d265dc7 dyld (433.5) <322C06B7-8878-311D-888C-C8FD2CA96FF3> /usr/lib/dyld
0x7fffcdac7000 - 0x7fffce8a0ff3 com.apple.AppKit (6.9 - 1504.83.101) <EC7BD195-F9E1-3E43-820A-5FDD0B2B0B67> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
0x7fffce8b2000 - 0x7fffce8b2fff com.apple.ApplicationServices (48 - 48) <4C71CBA8-47E4-38BF-BE3B-F20DF8667D5D> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices
0x7fffcff8c000 - 0x7fffd0425ff7 com.apple.CoreFoundation (6.9 - 1349.8) <09ED473E-5DE8-307F-B55C-16F6419236D5> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x7fffd0e51000 - 0x7fffd0e51fff com.apple.CoreServices (775.19 - 775.19) <7255917D-EFBB-3BE2-A8FD-DAD631BC0949> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
0x7fffd1a04000 - 0x7fffd1daaff3 com.apple.Foundation (6.9 - 1349.81) <730B7944-BB43-35D5-A546-9F6CCED4B9F3> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x7fffe41e5000 - 0x7fffe41e6ffb libSystem.B.dylib (1238.60.2) <FC9E9F13-3B18-305C-BE0A-97C7843652B0> /usr/lib/libSystem.B.dylib
0x7fffe431f000 - 0x7fffe4375ff7 libc++.1.dylib (307.5) <0B43BB5D-E6EB-3464-8DE9-B41AC8ED9D1C> /usr/lib/libc++.1.dylib
0x7fffe4376000 - 0x7fffe43a0fff libc++abi.dylib (307.3) <30199352-88BF-30BD-8CFF-2A4FBE247523> /usr/lib/libc++abi.dylib
0x7fffe4e93000 - 0x7fffe5265047 libobjc.A.dylib (709) <DC77AA6E-A4E4-326D-8D7F-82D63AA88F99> /usr/lib/libobjc.A.dylib
0x7fffe56b1000 - 0x7fffe56b5ff7 libcache.dylib (79) <093A4DAB-8385-3D47-A350-E20CB7CCF7BF> /usr/lib/system/libcache.dylib
0x7fffe56b6000 - 0x7fffe56c0fff libcommonCrypto.dylib (60092.50.5) <8A64D1B0-C70E-385C-92F0-E669079FDA90> /usr/lib/system/libcommonCrypto.dylib
0x7fffe56c1000 - 0x7fffe56c8fff libcompiler_rt.dylib (62) <55D47421-772A-32AB-B529-1A46C2F43B4D> /usr/lib/system/libcompiler_rt.dylib
0x7fffe56c9000 - 0x7fffe56d1fff libcopyfile.dylib (138) <819BEA3C-DF11-3E3D-A1A1-5A51C5BF1961> /usr/lib/system/libcopyfile.dylib
0x7fffe56d2000 - 0x7fffe5755fdf libcorecrypto.dylib (442.50.19) <65D7165E-2E71-335D-A2D6-33F78E2DF0C1> /usr/lib/system/libcorecrypto.dylib
0x7fffe5756000 - 0x7fffe5787fff libdispatch.dylib (703.50.37) <6582BAD6-ED27-3B30-B620-90B1C5A4AE3C> /usr/lib/system/libdispatch.dylib
0x7fffe5788000 - 0x7fffe578dffb libdyld.dylib (433.5) <EC3D88D2-3D40-3274-8E26-362C2D7352C8> /usr/lib/system/libdyld.dylib
0x7fffe578e000 - 0x7fffe578effb libkeymgr.dylib (28) <7AA011A9-DC21-3488-BF73-3B5B14D1FDD6> /usr/lib/system/libkeymgr.dylib
0x7fffe579c000 - 0x7fffe579cfff liblaunch.dylib (972.60.2) <D3306CFF-58AA-3C90-B06C-B70E80E60C5B> /usr/lib/system/liblaunch.dylib
0x7fffe579d000 - 0x7fffe57a2ff3 libmacho.dylib (898) <17D5D855-F6C3-3B04-B680-E9BF02EF8AED> /usr/lib/system/libmacho.dylib
0x7fffe57a3000 - 0x7fffe57a5ff3 libquarantine.dylib (85.50.1) <12448CC2-378E-35F3-BE33-9DC395A5B970> /usr/lib/system/libquarantine.dylib
0x7fffe57a6000 - 0x7fffe57a7ffb libremovefile.dylib (45) <38D4CB9C-10CD-30D3-8B7B-A515EC75FE85> /usr/lib/system/libremovefile.dylib
0x7fffe57a8000 - 0x7fffe57c0ff7 libsystem_asl.dylib (349.50.5) <096E4228-3B7C-30A6-8B13-EC909A64499A> /usr/lib/system/libsystem_asl.dylib
0x7fffe57c1000 - 0x7fffe57c1ff7 libsystem_blocks.dylib (67) <10DC5404-73AB-35B3-A277-A8AFECB476EB> /usr/lib/system/libsystem_blocks.dylib
0x7fffe57c2000 - 0x7fffe584ffef libsystem_c.dylib (1158.50.2) <E5AE5244-7D0C-36AC-8BB6-C7AE7EA52A4B> /usr/lib/system/libsystem_c.dylib
0x7fffe5850000 - 0x7fffe5853ffb libsystem_configuration.dylib (888.60.2) <BECC01A2-CA8D-31E6-BCDF-D452965FA976> /usr/lib/system/libsystem_configuration.dylib
0x7fffe5854000 - 0x7fffe5857fff libsystem_coreservices.dylib (41.4) <7D26DE79-B424-3450-85E1-F7FAB32714AB> /usr/lib/system/libsystem_coreservices.dylib
0x7fffe5858000 - 0x7fffe5870fff libsystem_coretls.dylib (121.50.4) <EC6FCF07-DCFB-3A03-9CC9-6DD3709974C6> /usr/lib/system/libsystem_coretls.dylib
0x7fffe5871000 - 0x7fffe5877fff libsystem_dnssd.dylib (765.50.9) <CC960215-0B1B-3822-A13A-3DDE96FA796F> /usr/lib/system/libsystem_dnssd.dylib
0x7fffe5878000 - 0x7fffe58a1ff7 libsystem_info.dylib (503.50.4) <611DB84C-BF70-3F92-8702-B9F28A900920> /usr/lib/system/libsystem_info.dylib
0x7fffe58a2000 - 0x7fffe58c4ff7 libsystem_kernel.dylib (3789.60.24) <6E9E485F-91F6-36B7-A125-AE91DC978BCC> /usr/lib/system/libsystem_kernel.dylib
0x7fffe58c5000 - 0x7fffe590cfe7 libsystem_m.dylib (3121.6) <86D499B5-BBDC-3D3B-8A4E-97AE8E6672A4> /usr/lib/system/libsystem_m.dylib
0x7fffe590d000 - 0x7fffe592bff7 libsystem_malloc.dylib (116.50.8) <A3D15F17-99A6-3367-8C7E-4280E8619C95> /usr/lib/system/libsystem_malloc.dylib
0x7fffe592c000 - 0x7fffe5985ffb libsystem_network.dylib (856.60.1) <369D0221-56CA-3C3E-9EDE-94B41CAE77B7> /usr/lib/system/libsystem_network.dylib
0x7fffe5986000 - 0x7fffe598fff3 libsystem_networkextension.dylib (563.60.2) <B021F2B3-8A75-3633-ABB0-FC012B8E9B0C> /usr/lib/system/libsystem_networkextension.dylib
0x7fffe5990000 - 0x7fffe5999ff3 libsystem_notify.dylib (165.20.1) <B8160190-A069-3B3A-BDF6-2AA408221FAE> /usr/lib/system/libsystem_notify.dylib
0x7fffe599a000 - 0x7fffe59a2fe7 libsystem_platform.dylib (126.50.8) <897462FD-B318-321B-A554-E61982630F7E> /usr/lib/system/libsystem_platform.dylib
0x7fffe59a3000 - 0x7fffe59adff7 libsystem_pthread.dylib (218.60.3) <B8FB5E20-3295-39E2-B5EB-B464D1D4B104> /usr/lib/system/libsystem_pthread.dylib
0x7fffe59ae000 - 0x7fffe59b1ff7 libsystem_sandbox.dylib (592.60.1) <DC780631-BD23-36B1-9376-668619E18D25> /usr/lib/system/libsystem_sandbox.dylib
0x7fffe59b2000 - 0x7fffe59b3ff3 libsystem_secinit.dylib (24.50.4) <F78B847B-3565-3E4B-98A6-F7AD40392E2D> /usr/lib/system/libsystem_secinit.dylib
0x7fffe59b4000 - 0x7fffe59bbffb libsystem_symptoms.dylib (532.50.47) <3390E07C-C1CE-348F-ADBD-2C5440B45EAA> /usr/lib/system/libsystem_symptoms.dylib
0x7fffe59bc000 - 0x7fffe59cfff7 libsystem_trace.dylib (518.60.2) <6B145B10-5874-3E89-90CD-D370DB475BA1> /usr/lib/system/libsystem_trace.dylib
0x7fffe59d0000 - 0x7fffe59d5ffb libunwind.dylib (35.3) <3D50D8A8-C460-334D-A519-2DA841102C6B> /usr/lib/system/libunwind.dylib
0x7fffe59d6000 - 0x7fffe59ffff7 libxpc.dylib (972.60.2) <1C9AF716-69DF-359F-85E9-7DFDE362F9A2> /usr/lib/system/libxpc.dylib
Model: MacBookAir7,2, BootROM MBA71.0166.B26, 2 processors, Intel Core i5, 1.8 GHz, 8 GB, SMC 2.27f2
Graphics: Intel HD Graphics 6000, Intel HD Graphics 6000, Built-In
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1600 MHz, 0x80CE, 0x4B3445364533303445452D45474345000000
Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1600 MHz, 0x80CE, 0x4B3445364533303445452D45474345000000
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x117), Broadcom BCM43xx 1.0 (7.21.171.126.1a2)
Bluetooth: Version 5.0.4f18, 3 services, 27 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
Serial ATA Device: APPLE SSD SM0128G, 121.33 GB
USB Device: USB 3.0 Bus
USB Device: BRCM20702 Hub
USB Device: Bluetooth USB Host Controller
USB Device: DataTraveler 2.0
Thunderbolt Bus: MacBook Air, Apple Inc., 27.2
I will attempt on my other MacBook Air and see if it is an update issue. I tried it on a plain MacBook Air with no build tools for wallets. |
|
|
|
How to participate in the Specs coin POS?How many COINS do I need?
Probably only a couple hundred coins is all you need. keep then in one group to get the weight to stake more often. When you get into the 10k - 100k of coins then you can group them into blocks to receive consistent staking. |
|
|
|
anyone have any working nodes?
Yes, still have a working node. If someone has a Antminer L3 they could solo mine to get the blockchain moving again. |
|
|
|
I registered www.lasvegascoin.net but the page still needs to be created. I will offer a bounty of 200 VGS for someone to create a nice webpage for us. Vegas I will host the website for you, if you need hosting. |
|
|
|
|
@vegasguy
Can I make a suggestion for your updates in your OP... Can you add the date of the latest update at the top of the OP so we can see if there is new info on the page.
I have been buried in other things away from Crypto and when I skim through my favourite projects I like to see the latest info. Sometimes it is hard to see if things have changed if there are no dates posted on the updates.
Your friend and supporter,
Midnight Miner
|
|
|
|
|
I am about a 5 hour drive from this company.
I am still waiting for an L3+ miner I ordered from the November batch. I received my L3+ from the November and December batch directly from Bitmain already. I am still waiting for the one I ordered through this company.
Any one else still waiting for their promised orders? We can send some people to check out the businesses directly and find the owners for answers.
|
|
|
|
Yobit can be a pain sometimes...
Yobit is always a pain  Especially their technical support, which responds a week or even a month to a simple question It seems to me that for the reputation of the coin this exchange is doing more harm than good And no discord so if the team does not the community can help but on the fly! Sorry but this project is failing big time. Has to be said... Amsterdam Coin has a channel on the Bitsend Slack chat: https://bitsend.slack.comI don't remember where the invite link is posted. |
|
|
|
Less than 2 days left in the Swap to v4 AMS!!! I still have an explorer running on v3 AMS here: http://ams.midnightminer.net/If you need a bootstrap to get your old wallet updated for the swap you are running out of time. If you are late to the swap notify Keesdewit as soon as possible so you do not miss out. Once the swap is completed I will remove the old block explorer and move to the new wallet version after all exchanges are confirmed on the new wallet so that all the coin movements on the old chain can still be verified by the community. |
|
|
|
Kees, Have you looked at my Block Explorer on the old chain lately? http://ams.midnightminer.net/I still have 30 connections to the wallet. There are still a few wallets running on the old chain (myself included). I need to get all my AMD coins together and get them to the swap. Hi midnight_miner, Why don't you configure your explorer for the new chain? If you send me the private keys then I can arrange the swap for you. When the swap ends I expect the old chain to stall because miners will leave when their rewards are not swapable anymore. Best regards, keesdewit I am currently setting up 2 new servers for Block Explorers and mining pools, so the new chain will be on the new server. |
|
|
|
Kees, Have you looked at my Block Explorer on the old chain lately? http://ams.midnightminer.net/I still have 30 connections to the wallet. There are still a few wallets running on the old chain (myself included). I need to get all my AMD coins together and get them to the swap. |
|
|
|
Wait, why is $BTA being removed from Bittrex?
It is not clear exactly why Bata is being de-listed. The official answer from Bittrex for the coins listed is that they do not give advance warning to developers or specify reasons for de-listing. Bittrex is protecting their own interests as well, so not giving a reason protects them from possible legal action. There are a couple theories as to why the de-listing and we are working on a resolution to hopefully stay listed on Bittrex. |
|
|
|
While we sort things out with Bittrex you can always monitor our wallets and other top wallets to see if any one bails on the project: http://bata.midnightminer.net/richlist@pc888 will be keeping us up-to-date on the progress of discussions with Bittrex and the outcome to keep our listing on the Bittrex Exchange. It was a confusing day for all of use following Bata, but we hope to have more details soon. The only thing the we have other than feedback from Bittrex operators is the following article: http://stockemperor.com/currencies/sec-purges-cryptocurrencies/(thank you mining4bacon on #Slack) for finding this. I am sure there will be more information coming out other news outlets throughout the day. |
|
|
|
how often are the rewards paid on midnight miner pool. Am I right in thinking worker name is wallet address? also could you give me complete url to set up mining. Thanks
Payouts run every couple hours, and minimum payout is 2 BTA. The stratum port list is available here: http://pool.midnightminer.net/getting_startedIf you are not sure of the optimum difficulty size, then start with the VarDiff on Port: 9814 |
|
|
|
Does anyone have a how to for compiling the qt file from the files off the website for the raspberry pi? You get 3 files:
amsterdamcoin-tx
amsterdamcoin-cli
amsterdamcoind
I usually compile from the git hub rep, but if I do that with AMS v.4.1 it just shows up as a pre-production version so wastes my time.
guess no help on this then? I am curious if you have successfully compiled qt on RaspPi 3 for other coins? Also which version of qt are you compiling against. 4 or 5? |
|
|
|
Here is an interesting experience, and I am wondering if anyone else has gone through this: Running Masternodes on a VPS with a Windows control wallet setup. Lost electricity at home where the Windows control wallet it running, but headless Linux Masternodes are out in the web so should be no issues. Restart control wallet and need to rebuild database because of abrupt shutdown. Now my config for Masternodes is no longer valid. When I start them they all report: Failed to start masternode.
Error: Invalid IP address.
masternode=xxxxxxxxx-x So I need to recreate my masternodes??? Am I missing something or doing something wrong? The whole premise of the VPS hosted Masternodes is to keep them running if my control wallet goes down. The Masternodes should continue running and collecting rewards if the control wallet is offline, since the blockchain holds the TXout that validates the Masternodes. Try to start your MN from console. Go to console of your control wallet and type "masternode start-missing". Before that, unlock your wallet. Cheers bud. @crazyivan Awesome thank you! I was using the buttons in the masternode window and getting the errors. Console commands did the trick. A little strange as you would think the buttons would have the same functionality as the console commands... My main peeve is that I lose my uptime on the Masternodes when technically they were never offline?!?! |
|
|
|
Here is an interesting experience, and I am wondering if anyone else has gone through this: Running Masternodes on a VPS with a Windows control wallet setup. Lost electricity at home where the Windows control wallet it running, but headless Linux Masternodes are out in the web so should be no issues. Restart control wallet and need to rebuild database because of abrupt shutdown. Now my config for Masternodes is no longer valid. When I start them they all report: Failed to start masternode.
Error: Invalid IP address.
masternode=xxxxxxxxx-x So I need to recreate my masternodes??? Am I missing something or doing something wrong? The whole premise of the VPS hosted Masternodes is to keep them running if my control wallet goes down. The Masternodes should continue running and collecting rewards if the control wallet is offline, since the blockchain holds the TXout that validates the Masternodes. |
|
|
|
|
Show Posts
