Move Entry Point Detection (Aptos)

Entry Point Identification (State-Changing Only)

In Move, public functions can be invoked from transaction scripts (Aptos) and typically modify state. In addition, all entry functions are entrypoints. Package-protected (public package) and friend (friend or public friend) functions should be excluded.

Aptos Move

// Public entry functions are entry points
public entry fun transfer(from: &signer, to: address, amount: u64) { }

// Public functions callable by other modules
public fun helper(): u64 { }

// Entry-only functions (can't be called by other modules)
entry fun private_entry(account: &signer) { }

Visibility Rules

Access Control Patterns

Signer-Based Control (Aptos)

// Admin check via signer
public entry fun admin_action(admin: &signer) {
    assert!(signer::address_of(admin) == @admin_address, E_NOT_ADMIN);
}

// Owner check via resource
public entry fun owner_action(owner: &signer) acquires Config {
    let config = borrow_global(@module_addr);
    assert!(signer::address_of(owner) == config.owner, E_NOT_OWNER);
}

Capability Pattern (Aptos)

// Capability resource
struct AdminCap has key, store {}

// Requires capability
public entry fun admin_action(admin: &signer) acquires AdminCap {
    assert!(exists(signer::address_of(admin)), E_NO_CAP);
}

Access Control Classification

Contract-Only Detection

Friend Functions

// Only callable by friend modules
public(friend) fun internal_callback() { }

// Friend declaration
friend other_module;

Module-to-Module Patterns

// Functions designed for other modules
public fun on_transfer_hook(amount: u64): bool {
    // Called by token module
}

Extraction Strategy

Aptos

1. Parse all .move files
2. Find module declarations
3. Extract functions with public entry or entry visibility
4. Check function body for:
   • signer::address_of comparisons → Role-based
   • exists<*Cap> checks → Capability-based
   • No access checks → Public (Unrestricted)

Move-Specific Considerations

1. Resource Model: Access control often through resource ownership
2. Capabilities: Cap suffix typically indicates capability pattern
3. Acquires: acquires Resource shows what global resources are accessed
4. Generic Types: Type parameters may carry capability constraints
5. Friend Visibility: public(friend) limits callers to declared friends

Common Gotchas

1. Init Functions: init or initialize often create initial capabilities
2. Module Upgrades: Check upgrade capability ownership
3. Phantom Types: Type parameters with phantom don't affect runtime